On Fri, 2012-09-07 at 09:37 +0300, Michael S. Tsirkin wrote:
> On Fri, Sep 07, 2012 at 09:32:37AM +0300, Michael S. Tsirkin wrote:
> > On Fri, Sep 07, 2012 at 09:23:22AM +0300, Michael S. Tsirkin wrote:
> > > On Tue, Aug 21, 2012 at 08:52:06PM +, Nicholas A. Bellinger wrote:
> > > > From: Nicho
From: Stefan Hajnoczi
This patch adds a new type of host device that drives the vhost_scsi
device. The syntax to add vhost-scsi is:
qemu -vhost-scsi id=vhost-scsi0,wwpn=...,tpgt=123
The virtio-scsi emulated device will make use of vhost-scsi to process
virtio-scsi requests inside the kernel
From: Stefan Hajnoczi
The path to /dev/vhost-net is currently hardcoded in vhost_dev_init().
This needs to be changed so that /dev/vhost-scsi can be used. Pass in
the device path instead of hardcoding it.
Signed-off-by: Stefan Hajnoczi
Cc: Paolo Bonzini
Cc: Michael S. Tsirkin
Signed-off-by:
From: Nicholas Bellinger
This QEMU patch sets VirtIOSCSIConfig->max_target=0 for vhost-scsi operation
to restrict virtio-scsi LLD guest scanning to max_id=0 (a single target ID
instance) when connected to individual tcm_vhost endpoints.
This ensures that virtio-scsi LLD only attempts to scan tar
From: Stefan Hajnoczi
This patch starts and stops vhost as the virtio device transitions
through its status phases. Vhost can only be started once the guest
reports its driver has successfully initialized, which means the
virtqueues have been set up by the guest.
v3: - Add vhost-scsi.h include
From: Nicholas Bellinger
This patch renames+moves the net_handle_fd_param() caller used to
obtain a file descriptor from either qemu_parse_fd() (the normal case)
or from monitor_get_fd() (migration case) into a generically prefixed
monitor_handle_fd_param() to be used by vhost-scsi code.
Also up
From: Nicholas Bellinger
Hello Anthony & Co,
This is the fourth installment to add host virtualized target support for
the mainline tcm_vhost fabric driver using Linux v3.6-rc into QEMU 1.3.0-rc.
The series is available directly from the following git branch:
git://git.kernel.org/pub/scm/vi
"Michael S. Tsirkin" writes:
> On Fri, Sep 07, 2012 at 09:15:46AM +0930, Rusty Russell wrote:
>> Paolo Bonzini writes:
>> > Instead, VIRTIO_NET_F_HOST_MUST_SEND_GARP would be a "negative" feature:
>> > if set, the host _may not_ rely on the guest to send a gARP. Similarly
>> > if VIRTIO_BALLOON
On Fri, Sep 07, 2012 at 09:32:37AM +0300, Michael S. Tsirkin wrote:
> On Fri, Sep 07, 2012 at 09:23:22AM +0300, Michael S. Tsirkin wrote:
> > On Tue, Aug 21, 2012 at 08:52:06PM +, Nicholas A. Bellinger wrote:
> > > From: Nicholas Bellinger
> > >
> > > Hi folks,
> > >
> > > This is the third
On Fri, Sep 07, 2012 at 09:23:22AM +0300, Michael S. Tsirkin wrote:
> On Tue, Aug 21, 2012 at 08:52:06PM +, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > Hi folks,
> >
> > This is the third RFC for vhost-scsi patches against mainline QEMU v1.1
>
> I rebased on top of 1.2
On Tue, Aug 21, 2012 at 08:52:06PM +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> Hi folks,
>
> This is the third RFC for vhost-scsi patches against mainline QEMU v1.1
I rebased on top of 1.2 and put this in my tree:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git pci
Pl
On Tue, Aug 21, 2012 at 08:52:09PM +, Nicholas A. Bellinger wrote:
> From: Stefan Hajnoczi
>
> This patch adds a new type of host device that drives the vhost_scsi
> device. The syntax to add vhost-scsi is:
>
> qemu -vhost-scsi id=vhost-scsi0,wwpn=...,tpgt=123
>
> The virtio-scsi emulate
mmu_notifier is the interface to broadcast the mm events to KVM, the
tracepoints introduced in this patch can trace all these events, it is
very helpful for us to notice and fix the bug caused by mm
Signed-off-by: Xiao Guangrong
---
include/trace/events/kvm.h | 129 +
Checking the return of kvm_mmu_get_page is unnecessary since it is
guaranteed by memory cache
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 3c10bca..98cf4bf 100644
--
This bug was triggered:
[ 4220.198458] BUG: unable to handle kernel paging request at fffe
[ 4220.203907] IP: [] put_page+0xf/0x34
..
[ 4220.237326] Call Trace:
[ 4220.237361] [] kvm_arch_destroy_vm+0xf9/0x101 [kvm]
[ 4220.237382] [] kvm_put_kvm+0xcc/0x127 [kvm]
[ 4220.237401] []
We can not directly call kvm_release_pfn_clean to release the pfn
since we can meet noslot pfn which is used to cache mmio info into
spte
Introduce mmu_release_pfn_clean to do this kind of thing
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 19 ++-
arch/x86/kv
On Tue, Aug 21, 2012 at 08:52:06PM +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> Hi folks,
>
> This is the third RFC for vhost-scsi patches against mainline QEMU v1.1
> to support the upstream tcm_vhost host virtualized target driver now
> available in v3.6-rc kernel code.
On Fri, Sep 07, 2012 at 09:15:46AM +0930, Rusty Russell wrote:
> Paolo Bonzini writes:
> > Instead, VIRTIO_NET_F_HOST_MUST_SEND_GARP would be a "negative" feature:
> > if set, the host _may not_ rely on the guest to send a gARP. Similarly
> > if VIRTIO_BALLOON_F_MUST_TELL_HOST is set, the guest _
>On 08/23/2012 03:07 PM, Wangpan wrote:
>> Hi all,
>> I got this error when I compile the source tarball "qemu-kvm-1.1.1.tar.gz"
>> and "qemu-kvm-1.1.0.tar.gz" and as well as codes clone from
>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git,
>> the compile command I used is "./configure &
On Fri, Sep 07, 2012 at 02:17:08AM +0200, Sasha Levin wrote:
> Hi Michael,
>
> On 09/06/2012 02:08 PM, Michael S. Tsirkin wrote:
> > Add multiqueue support to virtio network device.
> > Add a new feature flag VIRTIO_NET_F_MULTIQUEUE for this feature, a new
> > configuration field max_virtqueue_pai
Hi Michael,
On 09/06/2012 02:08 PM, Michael S. Tsirkin wrote:
> Add multiqueue support to virtio network device.
> Add a new feature flag VIRTIO_NET_F_MULTIQUEUE for this feature, a new
> configuration field max_virtqueue_pairs to detect supported number of
> virtqueues as well as a new command VI
On Fri, Sep 07, 2012 at 09:19:04AM +0930, Rusty Russell wrote:
> "Michael S. Tsirkin" writes:
>
> > On Thu, Sep 06, 2012 at 05:27:23PM +0930, Rusty Russell wrote:
> >> "Michael S. Tsirkin" writes:
> >> > Yes without checksum net core always linearizes packets, so yes it is
> >> > screwed.
> >> >
Paolo Bonzini writes:
> Instead, VIRTIO_NET_F_HOST_MUST_SEND_GARP would be a "negative" feature:
> if set, the host _may not_ rely on the guest to send a gARP. Similarly
> if VIRTIO_BALLOON_F_MUST_TELL_HOST is set, the guest _may not_ use
> ballooned pages directly.
>
> There are _no_ other negat
Avi Kivity writes:
> On 09/06/2012 06:23 PM, Peter Maydell wrote:
>> On 6 September 2012 16:16, Avi Kivity wrote:
>>> (and the APIC, if treated as one-large-register) is 4k)
>>
>> ...so don't do that then. Trying to treat the whole APIC
>> as a single "register" means you don't get any of the
>>
"Michael S. Tsirkin" writes:
> On Thu, Sep 06, 2012 at 05:27:23PM +0930, Rusty Russell wrote:
>> "Michael S. Tsirkin" writes:
>> > Yes without checksum net core always linearizes packets, so yes it is
>> > screwed.
>> > For -net, skb always allocates space for 17 frags + linear part so
>> > it s
Cornelia Huck writes:
> On Thu, 06 Sep 2012 11:56:31 +0930
> Rusty Russell wrote:
>
>> Cornelia Huck writes:
>>
>> > Add specifications for the new s390 specific virtio-ccw transport.
>> >
>> > Signed-off-by: Cornelia Huck
>>
>> Excellent. I have applied and pushed this revision.
>
> Cool.
On Thu, Sep 06, 2012 at 09:46:50AM +0200, Paolo Bonzini wrote:
> VIRTIO_BALLOON_F_MUST_TELL_HOST cannot be used properly because it is a
> "negative" feature: it tells you that silent defalte is not supported.
> Right now, QEMU refuses migration if the target does not support all the
> features tha
On Thu, Sep 06, 2012 at 06:43:36PM +0200, Paolo Bonzini wrote:
> Il 06/09/2012 14:08, Michael S. Tsirkin ha scritto:
> > +#define VIRTIO_NET_CTRL_STEERING_HOST 1
>
> You didn't change this occurrence.
Good catch, thanks!
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the bo
On 09/06/2012 09:56 AM, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Thursday, September 06, 2012 4:57 AM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; ag...@suse.de; Bhushan
>> Bharat-
>> R65777
>> Subject
On 25.07.2012, at 20:31, Michael Neuling wrote:
> Alexander Graf wrote:
>
>> After merging the register type check patches from Ben's tree, the
>> hv enabled booke implementation ceased to compile.
>>
>> This patch fixes things up so everyone's happy again.
>
> Is there a defconfig which catc
On Thu, Sep 06, 2012 at 03:00:47PM -0400, Don Slutz wrote:
> On 09/06/12 14:40, Eduardo Habkost wrote:
> >On Thu, Sep 06, 2012 at 12:28:05PM +0200, Andreas Färber wrote:
> >>Am 30.08.2012 21:20, schrieb Don Slutz:
> >>>This is primarily done so that the guest will think it is running
> >>>under vmw
On 09/06/12 14:40, Eduardo Habkost wrote:
On Thu, Sep 06, 2012 at 12:28:05PM +0200, Andreas Färber wrote:
Am 30.08.2012 21:20, schrieb Don Slutz:
This is primarily done so that the guest will think it is running
under vmware when hypervisor=vmware is specified as a property of a
cpu.
Also allo
On Thu, Sep 06, 2012 at 12:28:05PM +0200, Andreas Färber wrote:
> Am 30.08.2012 21:20, schrieb Don Slutz:
> > This is primarily done so that the guest will think it is running
> > under vmware when hypervisor=vmware is specified as a property of a
> > cpu.
> >
> > Also allow this to work in accel=
On 09/05/2012 08:41 AM, Li, Jiongxi wrote:
> With APICv virtual interrupt delivery feature, EOI write from non
> root mode doesn't cause VM-Exit unless set in EOI exit bitmap VMCS
> field. Basically there're two methods to manipulate EOI exit bitmap:
Should be folded into the previous patch, other
On 09/05/2012 08:41 AM, Li, Jiongxi wrote:
> - before returning to guest, RVI should be updated if any pending IRRs
process pending interrupts does that for you, so you only need this with
KVM_SET_APIC.
> - EOI exit bitmap controls whether an EOI write should cause VM-Exit.
> if set, a trap-lik
Il 06/09/2012 14:08, Michael S. Tsirkin ha scritto:
> +#define VIRTIO_NET_CTRL_STEERING_HOST 1
You didn't change this occurrence.
Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kern
On 09/05/2012 08:41 AM, Li, Jiongxi wrote:
> Virtual interrupt delivery avoids KVM to inject vAPIC interrupts
> manually, which is fully taken care of by the hardware. This needs
> some special awareness into existing interrupr injection path:
>
> - for pending interrupt, instead of direct injec
On 2012-09-06 18:06, Andreas Färber wrote:
> Am 06.09.2012 10:44, schrieb Jan Kiszka:
>> On 2012-08-30 20:30, Jan Kiszka wrote:
>>> This adds PCI device assignment for i386 targets using the classic KVM
>>> interfaces. This version is 100% identical to what is being maintained
>>> in qemu-kvm for s
https://bugzilla.kernel.org/show_bug.cgi?id=46101
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
Am 06.09.2012 10:44, schrieb Jan Kiszka:
> On 2012-08-30 20:30, Jan Kiszka wrote:
>> This adds PCI device assignment for i386 targets using the classic KVM
>> interfaces. This version is 100% identical to what is being maintained
>> in qemu-kvm for several years and is supported by libvirt as well.
On 09/05/2012 08:41 AM, Li, Jiongxi wrote:
> - APIC read doesn't cause VM-Exit
> - APIC write becomes trap-like
>
>
> +/* emulate APIC access in a trap manner */
> +int kvm_apic_write_nodecode(struct kvm_vcpu *vcpu, u32 offset)
> +{
> + u32 val;
> +
> + /* hw has done the conditional che
On 09/05/2012 08:40 AM, Li, Jiongxi wrote:
> The VMCS includes controls that enable the virtualization of interrupts and
> the Advanced Programmable Interrupt Controller (APIC).
> When these controls are used, the processor will emulate many accesses to the
> APIC, track the state of the virtual
On 09/05/2012 08:00 PM, Michael S. Tsirkin wrote:
> interrupt_bitmap is KVM_NR_INTERRUPTS bits in size,
> so just use that instead of hard-coded constants
> and math.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line
On 09/06/2012 06:23 PM, Peter Maydell wrote:
> On 6 September 2012 16:16, Avi Kivity wrote:
>> (and the APIC, if treated as one-large-register) is 4k)
>
> ...so don't do that then. Trying to treat the whole APIC
> as a single "register" means you don't get any of the
> advantages of "does this ke
On 6 September 2012 16:16, Avi Kivity wrote:
> (and the APIC, if treated as one-large-register) is 4k)
...so don't do that then. Trying to treat the whole APIC
as a single "register" means you don't get any of the
advantages of "does this kernel support this register?"
etc. Is there some reason I
On 09/06/2012 06:08 PM, Alexander Graf wrote:
>
>
> On 06.09.2012, at 10:48, Avi Kivity wrote:
>
>> On 09/05/2012 09:48 AM, Rusty Russell wrote:
>>> Peter Maydell writes:
On 1 September 2012 13:28, Rusty Russell wrote:
> Rusty Russell (8):
> KVM: ARM: Fix walk_msrs()
>
https://bugzilla.kernel.org/show_bug.cgi?id=43355
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
On 06.09.2012, at 10:48, Avi Kivity wrote:
> On 09/05/2012 09:48 AM, Rusty Russell wrote:
>> Peter Maydell writes:
>>> On 1 September 2012 13:28, Rusty Russell wrote:
Rusty Russell (8):
KVM: ARM: Fix walk_msrs()
KVM: Move KVM_SET_ONE_REG/KVM_GET_ONE_REG to generic cod
On 09/03/2012 03:24 PM, Gleb Natapov wrote:
> This series (or rather the last patch of it) takes different approach
> to "rep ins" optimization. Instead of writing separate fast path for
> it do the fast path inside emulator itself. This way nobody can say the
> code is not reused!
>
> Patch 1,2 a
On 08/16/2012 10:28 PM, siddhesh phadke wrote:
> I want to assign my own character device to guest. I tried going
> through code and found -chardev option.-chardev defines several
> backend options but I could not understand how they interact with
> guest. I also tried to search online but I got in
https://bugzilla.kernel.org/show_bug.cgi?id=43311
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
On 08/22/2012 06:06 PM, Peter Lieven wrote:
> Hi,
>
> has anyone ever tested to run memtest with -cpu host flag passed to
> qemu-kvm?
> For me it resets when probing the chipset. With -cpu qemu64 it works
> just fine.
>
> Maybe this is specific to memtest, but it might be sth that can happen
> in
> -Original Message-
> From: Wood Scott-B07421
> Sent: Thursday, September 06, 2012 4:57 AM
> To: Bhushan Bharat-R65777
> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; ag...@suse.de; Bhushan
> Bharat-
> R65777
> Subject: Re: [PATCH 6/6] KVM: booke/bookehv: Add debug stub support
>
>
On 09/05/2012 09:48 AM, Rusty Russell wrote:
> Peter Maydell writes:
>> On 1 September 2012 13:28, Rusty Russell wrote:
>>> Rusty Russell (8):
>>> KVM: ARM: Fix walk_msrs()
>>> KVM: Move KVM_SET_ONE_REG/KVM_GET_ONE_REG to generic code.
>>> KVM: Add KVM_REG_SIZE() helper.
>>>
On 09/04/2012 04:59 PM, Alexander Graf wrote:
>>
>> Not is you pack the pointer in a __u64, which is what we do to preserve
>> padding. Then it is only s390 which needs extra love.
>
> I doubt that anyone wants to run 31-bit user space on an s390x system. In
> fact, I wouldn't be surprised if e
On 08/22/2012 03:47 PM, Xiao Guangrong wrote:
> On 08/22/2012 08:06 PM, Avi Kivity wrote:
>> On 08/21/2012 06:03 AM, Xiao Guangrong wrote:
>>> Introduce write_readonly_mem in mmio-exit-info to indicate this exit is
>>> caused by write access on readonly memslot
>>
>> Please document this in chapte
On 08/23/2012 03:07 PM, Wangpan wrote:
> Hi all,
> I got this error when I compile the source tarball "qemu-kvm-1.1.1.tar.gz"
> and "qemu-kvm-1.1.0.tar.gz" and as well as codes clone from
> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git,
> the compile command I used is "./configure && make".
On 08/28/2012 08:38 AM, Bo Yang wrote:
> Signed-off-by: Bo Yang
Please copy the qemu mailing list on qemu patches.
I'm not sure whether we should document kvm_stat; I'd like to remove it
once 'perf' (from the kernel tools/perf directory) gains the same
capabilities.
--
error compiling commit
On 09/04/2012 06:07 PM, Liu, Jinsong wrote:
> From 728a17e2de591b557c3c8ba31076b4bf2ca5ab42 Mon Sep 17 00:00:00 2001
> From: Liu, Jinsong
> Date: Wed, 5 Sep 2012 03:18:15 +0800
> Subject: [PATCH] KVM: tsc deadline timer works only when hrtimer high
> resolution configured
>
> This is for 2 reaso
On Thu, 06 Sep 2012 11:56:31 +0930
Rusty Russell wrote:
> Cornelia Huck writes:
>
> > Add specifications for the new s390 specific virtio-ccw transport.
> >
> > Signed-off-by: Cornelia Huck
>
> Excellent. I have applied and pushed this revision.
Cool.
Unfortunately, we just discovered that
On Thu, 2012-09-06 at 12:14 +0200, Andrew Holway wrote:
> On Sep 5, 2012, at 4:02 PM, Avi Kivity wrote:
>
> > On 09/04/2012 03:04 PM, Myklebust, Trond wrote:
> >> On Tue, 2012-09-04 at 11:31 +0200, Andrew Holway wrote:
> >>> Hello.
> >>>
> >>> # Avi Kivity avi(a)redhat recommended I copy kvm in o
Howdy!
Can you please help me to use virtio in the most efficient way
possible?
I'm building a userspace hypervisor switch called Snabb Switch at
http://www.github.com/SnabbCo/snabbswitch. I want the performance to
be competitive with kernel-space switches like the Linux bridge and
Open vSwitch.
On 08/24/2012 09:54 PM, Marcelo Tosatti wrote:
> Paul, does that work for you.
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordom
Il 06/09/2012 14:51, Michael S. Tsirkin ha scritto:
> On Thu, Sep 06, 2012 at 02:13:14PM +0200, Paolo Bonzini wrote:
>> Il 06/09/2012 12:53, Michael S. Tsirkin ha scritto:
It is useful because it lets guests inflate the balloon aggressively,
and then use ballooned-out pages even in places
Critical exception on 64-bit booke uses user-visible SPRG3 as scratch.
Restore VDSO information in SPRG3 on exception prolog.
Use a common sprg3 field in PACA for all powerpc64 architectures.
Signed-off-by: Mihai Caraman
---
arch/powerpc/include/asm/kvm_book3s_asm.h |1 -
arch/powerpc/includ
On Thu, Sep 06, 2012 at 02:13:14PM +0200, Paolo Bonzini wrote:
> Il 06/09/2012 12:53, Michael S. Tsirkin ha scritto:
> >> It is useful because it lets guests inflate the balloon aggressively,
> >> and then use ballooned-out pages even in places where the guest OS
> >> cannot sleep, such as kmalloc(
Il 06/09/2012 12:53, Michael S. Tsirkin ha scritto:
>> It is useful because it lets guests inflate the balloon aggressively,
>> and then use ballooned-out pages even in places where the guest OS
>> cannot sleep, such as kmalloc(GFP_ATOMIC).
>
> Interesting.
> Do you intend to develop a driver patc
Add multiqueue support to virtio network device.
Add a new feature flag VIRTIO_NET_F_MULTIQUEUE for this feature, a new
configuration field max_virtqueue_pairs to detect supported number of
virtqueues as well as a new command VIRTIO_NET_CTRL_STEERING to program
packet steering.
Signed-off-by: Mich
On 09/06/2012 02:27 PM, Tomoki Sekiyama wrote:
> This RFC patch series provides facility to dedicate CPUs to KVM guests
> and enable the guests to handle interrupts from passed-through PCI devices
> directly (without VM exit and relay by the host).
>
> With this feature, we can improve throughput
Enable virtualization when slave CPUs are activated, and disable when
the CPUs are dying using slave CPU notifier call chain.
In x86, TSC kHz must also be initialized by tsc_khz_changed when the
new slave CPUs are activated.
Signed-off-by: Tomoki Sekiyama
Cc: Avi Kivity
Cc: Marcelo Tosatti
Cc:
If the slave CPU receives an interrupt in running a guest, current
implementation must once go back to onilne CPUs to handle the interupt.
This behavior will be replaced by later patch, which introduces direct
interrupt handling mechanism by the guest.
Signed-off-by: Tomoki Sekiyama
Cc: Avi Kivi
Add some fix-ups that proxy slab operations on online CPUs for the guest,
in order to avoid touching slab on slave CPUs where some slab functions
are not activated.
Currently, slab may be touched on slave CPUs in following 3 cases.
For each cases, the fix-ups below are introduced:
* kvm_mmu_commi
Add an interface to set/get slave CPU dedicated to the vCPUs.
By calling ioctl with KVM_GET_SLAVE_CPU, users can get the slave CPU id
for the vCPU. -1 is returned if a slave CPU is not set.
By calling ioctl with KVM_SET_SLAVE_CPU, users can dedicate the specified
slave CPU to the vCPU. The CPU mu
Add path to migrate execution of vcpu_enter_guest to a slave CPU when
vcpu->arch.slave_cpu is set.
After moving to the slave CPU, it goes back to the online CPU when the
guest is exited by reasons that cannot be handled by the slave CPU only
(e.g. handling async page faults).
On migration, kvm_ar
Adds a facility to use hrtimer on slave CPUs.
To initialize hrtimer when slave CPUs are activated, and to shutdown hrtimer
when slave CPUs are stopped, this patch adds the slave cpu notifier chain,
which call registered callbacks when slave CPUs are up, dying, and died.
The registered callbacks a
Add a facility of using offlined CPUs as slave CPUs. Slave CPUs are
specialized to exclusively run functions specified by online CPUs,
which do not run user processes.
To use this feature, build the kernel with CONFIG_SLAVE_CPU=y.
A slave CPU is launched by calling cpu_slave_up() when the CPU is
Split memory hotplug function from cpu_up() as cpu_memory_up(), which will
be used for assigning memory area to off-lined cpus at following patch
in this series.
Signed-off-by: Tomoki Sekiyama
Cc: Avi Kivity
Cc: Marcelo Tosatti
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
---
i
Make interrupts on slave CPUs handled by guests without VM EXIT.
This reduces CPU usage by the host to transfer interrupts of assigned
PCI devices from the host to guests. It also reduces cost of VM EXIT
and quickens response of guests to the interrupts.
When a slave CPU is dedicated to a vCPU, ex
When a PCI device is assigned to a guest running on slave CPUs, this
routes the device's MSI/MSI-X interrupts directly to the guest.
Because the guest uses a different interrupt vector from the host,
vector remapping is required. This is safe because slave CPUs only handles
interrupts for the assi
For slave CPUs, it is inapropriate to request TLB flush using IPI.
because the IPI may be sent to a KVM guest when the slave CPU is running
the guest with direct interrupt routing.
Instead, it registers a TLB flush request in per-cpu bitmask and send a NMI
to interrupt execution of the guest. Then
Enable direct access to EOI MSR of x2apic to accelerate guests.
This accelerate handling of interrupts delivered directly to guest from
passed-through PCI devices. When a virtual IRQ is injected, this feature
is disabled in order to route following EOI to virtual APIC. Then, it is
enabled again aft
Add some definitions to use PIN_BASED_PREEMPTION_TIMER.
When PIN_BASED_PREEMPTION_TIMER is enabled, the guest will exit
with reason=EXIT_REASON_PREEMPTION_TIMER when the counter specified in
VMX_PREEMPTION_TIMER_VALUE becomes 0.
This patch also adds a dummy handler for EXIT_REASON_PREEMPTION_TIMER
Initialize rcu related variables to avoid warnings about RCU usage while
slave CPUs is running specified functions. Also notify RCU subsystem before
the slave CPU is entered into idle state.
Signed-off-by: Tomoki Sekiyama
Cc: Avi Kivity
Cc: Marcelo Tosatti
Cc: Thomas Gleixner
Cc: Ingo Molnar
Avoid exiting from a guest on slave CPU even if HLT instruction is
executed. Since the slave CPU is dedicated to a vCPU, exit on HLT is
not required, and avoiding VM exit will improve the guest's performance.
This is a partial revert of
10166744b80a ("KVM: VMX: remove yield_on_hlt")
Cc:
Enable APIC to handle interrupts on slave CPUs, and enables interrupt
routing to slave CPUs by setting IRQ affinity.
As slave CPUs which run a KVM guest handle external interrupts directly in
the vCPUs, the guest's vector/IRQ mapping is different from the host's.
That requires interrupts to be rou
On 09/06/2012 02:31 PM, Avi Kivity wrote:
> On 09/06/2012 02:27 PM, Tomoki Sekiyama wrote:
>> Split memory hotplug function from cpu_up() as cpu_memory_up(), which will
>> be used for assigning memory area to off-lined cpus at following patch
>> in this series.
>>
>
> Can post a summary containin
Since NMI can not be disabled around VM enter, there is a race between
receiving NMI to kick a guest and entering the guests on slave CPUs.If the
NMI is received just before entering VM, after the NMI handler is invoked,
it continues entering the guest and the effect of the NMI will be lost.
This
On 09/06/2012 02:27 PM, Tomoki Sekiyama wrote:
> Split memory hotplug function from cpu_up() as cpu_memory_up(), which will
> be used for assigning memory area to off-lined cpus at following patch
> in this series.
>
Can post a summary containing both the general outline for people
reading this f
Provide direct control of local APIC timer of slave CPUs to the guest.
The timer interrupt does not cause VM exit if direct interrupt delivery is
enabled. To handle the timer correctly, this makes the guest occupy the
local APIC timer.
If the host supports x2apic, this expose TMICT and TMCCT to th
Add a facility to use IRQ vector different from online CPUs on slave CPUs.
When alternative vector for IRQ is registered by remap_slave_vector_irq()
and the IRQ affinity is set only to slave CPUs, the device is configured
to use the alternative vector.
Current patch only supports MSI and Intel CP
Add trace event "kvm_set_direct_interrupt" to trace enabling/disabling
direct interrupt delivery on slave CPUs. At the event, the guest rip and
whether the feature is enabled or not is logged.
Signed-off-by: Tomoki Sekiyama
Cc: Avi Kivity
Cc: Marcelo Tosatti
Cc: Thomas Gleixner
Cc: Ingo Molnar
Page faults which occured by the guest running on slave CPUs cannot be
handled on slave CPUs because it is running on idle process context.
With this patch, the page fault happened in a slave CPU is notified to
online CPU using struct kvm_access_fault, and is handled after the
user-process for the
This RFC patch series provides facility to dedicate CPUs to KVM guests
and enable the guests to handle interrupts from passed-through PCI devices
directly (without VM exit and relay by the host).
With this feature, we can improve throughput and response time of the device
and the host's CPU usage
On Thu, Sep 06, 2012 at 11:57:22AM +0200, Paolo Bonzini wrote:
> Il 06/09/2012 11:44, Michael S. Tsirkin ha scritto:
> >> In fact, it's not clear how the driver should use the feature. My guess
> >> is that, if it wants to use silent deflate, it tries to negotiate
> >> VIRTIO_BALLOON_F_MUST_TELL_H
Am 30.08.2012 21:20, schrieb Don Slutz:
> This is primarily done so that the guest will think it is running
> under vmware when hypervisor=vmware is specified as a property of a
> cpu.
>
> Also allow this to work in accel=tcg mode.
>
> The new cpu properties hyper_level, hyper_extra, hyper_extra_
On Sep 5, 2012, at 4:02 PM, Avi Kivity wrote:
> On 09/04/2012 03:04 PM, Myklebust, Trond wrote:
>> On Tue, 2012-09-04 at 11:31 +0200, Andrew Holway wrote:
>>> Hello.
>>>
>>> # Avi Kivity avi(a)redhat recommended I copy kvm in on this. It would also
>>> seem relevent to libvirt. #
>>>
>>> I hav
Il 06/09/2012 11:44, Michael S. Tsirkin ha scritto:
>> In fact, it's not clear how the driver should use the feature. My guess
>> is that, if it wants to use silent deflate, it tries to negotiate
>> VIRTIO_BALLOON_F_MUST_TELL_HOST, and can use silent deflate if
>> negotiation fails. This is again
On Thu, Sep 06, 2012 at 11:24:02AM +0200, Paolo Bonzini wrote:
> Il 06/09/2012 10:47, Michael S. Tsirkin ha scritto:
> >> > - a migration from non-MUST_TELL_HOST to MUST_TELL_HOST will succeed,
> >> > which is wrong;
> >> >
> >> > - a migration from MUST_TELL_HOST to non-MUST_TELL_HOST will fail,
Message has been rejected - attachment type disallowed.
--
This message was created automatically by mail delivery software.
Message violated a policy rule set up by the domain administrator
Delivery failed for the following recipient(s):
dso...@meed-
Il 06/09/2012 10:47, Michael S. Tsirkin ha scritto:
>> > - a migration from non-MUST_TELL_HOST to MUST_TELL_HOST will succeed,
>> > which is wrong;
>> >
>> > - a migration from MUST_TELL_HOST to non-MUST_TELL_HOST will fail, which
>> > is useless.
>> >
>> > Add instead a new feature VIRTIO_BALLOO
1 - 100 of 112 matches
Mail list logo
