Re: [GIT PULL 0/5] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, > > - Arnaldo > > The following changes since commit 43e41adc9e8c36545888d78fed2ef8d102a938dc: > > perf record: Add ability to sample call branches (2015-10-20 10:30:55 +0200) > > are

Re: [PATCH 0/3] kvmtool: tiny init fox x86_64

Hi Oleg, On 10/19/2015 01:59 PM, Oleg Nesterov wrote: Yesterday I discovered kvmtool and it looks really cool! Thanks! Looks like, it does exactly what I need. But the static /virt/init doesn't look good. This series lessens the size of lkvm binary from 1045952 to 196200 bytes on x86_64, but

Re: Difference between vcpu_load and kvm_sched_in ?

On 10/21/15 2:46 PM, Paolo Bonzini wrote: On 21/10/2015 00:57, Wanpeng Li wrote: kvm_sched_out and kvm_sched_in are part of KVM's preemption hooks. The hooks are registered only between vcpu_load and vcpu_put, therefore they know that the mutex is taken. The sequence will go like this:

Re: [PATCH v2 0/3] target-i386: save/restore vcpu's TSC rate during migration

On Tue, Oct 20, 2015 at 03:22:51PM +0800, Haozhong Zhang wrote: > This patchset enables QEMU to save/restore vcpu's TSC rate during the > migration. When cooperating with KVM which supports TSC scaling, guest > programs can observe a consistent guest TSC rate even though they are > migrated among

Re: [PATCH v2 3/3] target-i386: load the migrated vcpu's TSC rate

On Tue, Oct 20, 2015 at 03:22:54PM +0800, Haozhong Zhang wrote: > Set vcpu's TSC rate to the migrated value (if any). If KVM supports TSC > scaling, guest programs will observe TSC increasing in the migrated rate > other than the host TSC rate. > > The loading is controlled by a new cpu option

Re: [PATCH net-next RFC 1/2] vhost: introduce vhost_has_work()

On Thu, Oct 22, 2015 at 01:27:28AM -0400, Jason Wang wrote: > This path introduces a helper which can give a hint for whether or not > there's a work queued in the work list. > > Signed-off-by: Jason Wang > --- > drivers/vhost/vhost.c | 6 ++ > drivers/vhost/vhost.h | 1

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On Thursday 22 October 2015 11:42:02 Eric Auger wrote: > Currently reset lookup is done on probe. This introduces a > race with new registration mechanism in the case where the > vfio-platform driver is bound to the device before its module > is loaded: on the load, the probe happens which

Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration

On 10/22/2015 12:13 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 11:41:59 Eric Auger wrote: >> This patch adds the reset function registration/unregistration. >> >> Signed-off-by: Eric Auger > > Looks good, except one thing: >> @@ -70,6 +69,8 @@ int

Re: [PATCH 14/23] userfaultfd: wake pending userfaults

On Thu, May 14, 2015 at 07:31:11PM +0200, Andrea Arcangeli wrote: > @@ -255,21 +259,23 @@ int handle_userfault(struct vm_area_struct *vma, > unsigned long address, >* through poll/read(). >*/ > __add_wait_queue(>fault_wqh, ); > - for (;;) { > -

Re: [PATCH v2 5/6] vfio: platform: use list of registered reset function

On 10/22/2015 12:19 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 11:42:01 Eric Auger wrote: >> Remove the static lookup table and use the dynamic list of registered >> reset functions instead. Also load the reset module through its alias. >> The reset struct module pointer is stored in

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

Hi Arnd, On 10/22/2015 12:29 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 11:42:02 Eric Auger wrote: >> Currently reset lookup is done on probe. This introduces a >> race with new registration mechanism in the case where the >> vfio-platform driver is bound to the device before its

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On Thursday 22 October 2015 13:40:16 Eric Auger wrote: > On 10/22/2015 12:29 PM, Arnd Bergmann wrote: > > On Thursday 22 October 2015 11:42:02 Eric Auger wrote: > >> Currently reset lookup is done on probe. This introduces a > >> race with new registration mechanism in the case where the > >>

Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration

On Thursday 22 October 2015 13:54:42 Eric Auger wrote: > On 10/22/2015 12:13 PM, Arnd Bergmann wrote: > > On Thursday 22 October 2015 11:41:59 Eric Auger wrote: > >> This patch adds the reset function registration/unregistration. > >> > >> Signed-off-by: Eric Auger > > > >

Re: [PATCH 2/2] KVM: arm/arm64: Merge vgic_set_lr() and vgic_sync_lr_elrsr()

On Fri, Oct 02, 2015 at 05:44:29PM +0300, Pavel Fedin wrote: > Now we see that vgic_set_lr() and vgic_sync_lr_elrsr() are always used > together. Merge them into one function, saving from second vgic_ops > dereferencing every time. > > Additionally, remove unnecessary vgic_set_lr() in

Re: [PATCH v2 2/2] KVM/arm: enable enhanced armv7 fp/simd lazy switch

On Tue, Oct 20, 2015 at 06:10:59PM -0700, Mario Smarduch wrote: > > > On 10/20/2015 12:24 AM, Christoffer Dall wrote: > > On Mon, Oct 19, 2015 at 04:25:04PM -0700, Mario Smarduch wrote: > >> > >> > >> On 10/19/2015 3:14 AM, Christoffer Dall wrote: > >>> On Sat, Sep 26, 2015 at 04:43:29PM -0700,

Re: [PATCH 1/2] KVM: arm/arm64: Optimize away redundant LR tracking

On Fri, Oct 02, 2015 at 05:44:28PM +0300, Pavel Fedin wrote: > Currently we use vgic_irq_lr_map in order to track which LRs hold which > IRQs, and lr_used bitmap in order to track which LRs are used or free. > > vgic_irq_lr_map is actually used only for piggy-back optimization, and > can be

[PATCH v2 5/6] vfio: platform: use list of registered reset function

Remove the static lookup table and use the dynamic list of registered reset functions instead. Also load the reset module through its alias. The reset struct module pointer is stored in vfio_platform_device. We also remove the useless struct device pointer parameter in vfio_platform_get_reset.

[PATCH v2 4/6] vfio: platform: add compat in vfio_platform_device

Let's retrieve the compatibility string on probe and store it in the vfio_platform_device struct Signed-off-by: Eric Auger --- drivers/vfio/platform/vfio_platform_common.c | 15 --- drivers/vfio/platform/vfio_platform_private.h | 1 + 2 files changed, 9

Re: [PATCH v2 1/6] vfio: platform: add capability to register a reset function

On Thursday 22 October 2015 11:41:57 Eric Auger wrote: > In preparation for subsequent changes in reset function lookup, > lets introduce a dynamic list of reset combos (compat string, > reset module, reset function). The list can be populated/voided with > two new functions,

[PATCH v2 2/6] vfio: platform: reset: add vfio_platform_reset_private.h

This header is to be included in all vfio reset modules. It defines the module_vfio_reset_handler macro whose role is - to define a module alias - implement module init/exit function which respectively registers and unregisters the reset function. Signed-off-by: Eric Auger

Re: [PATCH v2 2/6] vfio: platform: reset: add vfio_platform_reset_private.h

On Thursday 22 October 2015 11:41:58 Eric Auger wrote: > v2: creation > - this defines the module_vfio_reset_handler macro as suggested by Arnd > > Although Arnd suggested me to remove the vfio_platform_register_reset > symbol_get (since the module manager can handle the case where the >

Re: [PATCH net-next RFC 2/2] vhost_net: basic polling support

On Thu, Oct 22, 2015 at 01:27:29AM -0400, Jason Wang wrote: > This patch tries to poll for new added tx buffer for a while at the > end of tx processing. The maximum time spent on polling were limited > through a module parameter. To avoid block rx, the loop will end it > there's new other works

[PATCH v2 1/6] vfio: platform: add capability to register a reset function

In preparation for subsequent changes in reset function lookup, lets introduce a dynamic list of reset combos (compat string, reset module, reset function). The list can be populated/voided with two new functions, vfio_platform_register/unregister_reset. Those are not yet used in this patch.

[PATCH v2 0/6] VFIO platform reset module rework

This series fixes the current implementation by getting rid of the usage of __symbol_get which caused a compilation issue with CONFIG_MODULES disabled. On top of this, the usage of MODULE_ALIAS makes possible to add a new reset module without being obliged to update the framework. The new

Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration

On Thursday 22 October 2015 11:41:59 Eric Auger wrote: > This patch adds the reset function registration/unregistration. > > Signed-off-by: Eric Auger Looks good, except one thing: > @@ -70,6 +69,8 @@ int vfio_platform_calxedaxgmac_reset(struct > vfio_platform_device

Re: [PATCH v2 5/6] vfio: platform: use list of registered reset function

On Thursday 22 October 2015 11:42:01 Eric Auger wrote: > Remove the static lookup table and use the dynamic list of registered > reset functions instead. Also load the reset module through its alias. > The reset struct module pointer is stored in vfio_platform_device. > > We also remove the

[PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration

This patch adds the reset function registration/unregistration. Signed-off-by: Eric Auger --- v1 -> v2: - uses the module_vfio_reset_handler macro - add pr_info on vfio reset - do not export vfio_platform_calxedaxgmac_reset symbol anymore ---

[PATCH v2 6/6] vfio: platform: move get/put reset at open/release

Currently reset lookup is done on probe. This introduces a race with new registration mechanism in the case where the vfio-platform driver is bound to the device before its module is loaded: on the load, the probe happens which triggers the reset module load which itself attempts to get the symbol

Re: Difference between vcpu_load and kvm_sched_in ?

On 21/10/2015 19:21, Yacine HEBBAL wrote: > If I correctly understood you last paragraph, it is better to use vm_ioctl > to do generic processing that doesn't rely on a given VCPU and hence I won't > need to use "CPU_FOREACH, run_on_cpu and current_cpu". Right. On the other hand, you

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On Thursday 22 October 2015 15:26:55 Eric Auger wrote: > >> @@ -181,6 +182,8 @@ static int vfio_platform_open(void *device_data) > >> if (ret) > >> goto err_irq; > >> > >> + vfio_platform_get_reset(vdev); > >> + > >> if

Re: [PATCH 14/23] userfaultfd: wake pending userfaults

On Thu, Oct 22, 2015 at 03:38:24PM +0200, Peter Zijlstra wrote: > On Thu, Oct 22, 2015 at 03:20:15PM +0200, Andrea Arcangeli wrote: > > > If schedule spontaneously wakes up a task in TASK_KILLABLE state that > > would be a bug in the scheduler in my view. Luckily there doesn't seem > > to be such

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On 10/22/2015 04:10 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 15:26:55 Eric Auger wrote: @@ -181,6 +182,8 @@ static int vfio_platform_open(void *device_data) if (ret) goto err_irq; +

Re: [RFC Patch 12/12] IXGBEVF: Track dma dirty pages

On Thu, Oct 22, 2015 at 12:37:44AM +0800, Lan Tianyu wrote: > Migration relies on tracking dirty page to migrate memory. > Hardware can't automatically mark a page as dirty after DMA > memory access. VF descriptor rings and data buffers are modified > by hardware when receive and transmit data. To

Re: [RFC Patch 10/12] IXGBEVF: Add lock to protect tx/rx ring operation

On Thu, Oct 22, 2015 at 12:37:42AM +0800, Lan Tianyu wrote: > Ring shifting during restoring VF function maybe race with original > ring operation(transmit/receive package). This patch is to add tx/rx > lock to protect ring related data. > > Signed-off-by: Lan Tianyu

Re: [Qemu-devel] [RFC Patch 05/12] IXGBE: Add new sysfs interface of "notify_vf"

On Wed, Oct 21, 2015 at 01:52:48PM -0700, Alexander Duyck wrote: > Also have you even considered the MSI-X configuration on the VF? I haven't > seen anything anywhere that would have migrated the VF's MSI-X configuration > from BAR 3 on one system to the new system. Hypervisors do this for

Re: [PATCH v2 0/3] target-i386: save/restore vcpu's TSC rate during migration

On Thu, Oct 22, 2015 at 04:45:21PM -0200, Eduardo Habkost wrote: > On Tue, Oct 20, 2015 at 03:22:51PM +0800, Haozhong Zhang wrote: > > This patchset enables QEMU to save/restore vcpu's TSC rate during the > > migration. When cooperating with KVM which supports TSC scaling, guest > > programs can

Re: [PATCH v2 3/3] target-i386: load the migrated vcpu's TSC rate

On Thu, Oct 22, 2015 at 04:11:37PM -0200, Eduardo Habkost wrote: > On Tue, Oct 20, 2015 at 03:22:54PM +0800, Haozhong Zhang wrote: > > Set vcpu's TSC rate to the migrated value (if any). If KVM supports TSC > > scaling, guest programs will observe TSC increasing in the migrated rate > > other than

Re: [PATCH v2 3/3] target-i386: load the migrated vcpu's TSC rate

On Thu, Oct 22, 2015 at 04:11:37PM -0200, Eduardo Habkost wrote: > On Tue, Oct 20, 2015 at 03:22:54PM +0800, Haozhong Zhang wrote: > > Set vcpu's TSC rate to the migrated value (if any). If KVM supports TSC > > scaling, guest programs will observe TSC increasing in the migrated rate > > other than

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On 10/22/2015 02:05 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 13:40:16 Eric Auger wrote: >> On 10/22/2015 12:29 PM, Arnd Bergmann wrote: >>> On Thursday 22 October 2015 11:42:02 Eric Auger wrote: Currently reset lookup is done on probe. This introduces a race with new

Re: [RFC Patch 11/12] IXGBEVF: Migrate VF statistic data

On Thu, Oct 22, 2015 at 12:37:43AM +0800, Lan Tianyu wrote: > VF statistic regs are read-only and can't be migrated via writing back > directly. > > Currently, statistic data returned to user space by the driver is not equal > to value of statistic regs. VF driver records value of statistic regs

Re: [Qemu-devel] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC

On Thu, Oct 22, 2015 at 12:37:32AM +0800, Lan Tianyu wrote: > This patchset is to propose a new solution to add live migration support for > 82599 > SRIOV network card. > > Im our solution, we prefer to put all device specific operation into VF and > PF driver and make code in the Qemu more

Re: [Qemu-devel] [RFC Patch 06/12] IXGBEVF: Add self emulation layer

On Wed, Oct 21, 2015 at 01:58:19PM -0700, Alexander Duyck wrote: > On 10/21/2015 09:37 AM, Lan Tianyu wrote: > >In order to restore VF function after migration, add self emulation layer > >to record regs' values during accessing regs. > > > >Signed-off-by: Lan Tianyu > >---

Re: [Qemu-devel] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC

On Thu, 2015-10-22 at 15:32 +0300, Michael S. Tsirkin wrote: > On Wed, Oct 21, 2015 at 01:20:27PM -0600, Alex Williamson wrote: > > The trouble here is that the VF needs to be unplugged prior to the start > > of migration because we can't do effective dirty page tracking while the > > device is

Re: [Qemu-devel] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC

On Thu, Oct 22, 2015 at 07:01:01AM -0600, Alex Williamson wrote: > On Thu, 2015-10-22 at 15:32 +0300, Michael S. Tsirkin wrote: > > On Wed, Oct 21, 2015 at 01:20:27PM -0600, Alex Williamson wrote: > > > The trouble here is that the VF needs to be unplugged prior to the start > > > of migration

Re: [PATCH 14/23] userfaultfd: wake pending userfaults

On Thu, Oct 22, 2015 at 03:20:15PM +0200, Andrea Arcangeli wrote: > If schedule spontaneously wakes up a task in TASK_KILLABLE state that > would be a bug in the scheduler in my view. Luckily there doesn't seem > to be such a bug, or at least we never experienced it. Well, there will be a

Re: [PATCH v2 3/6] vfio: platform: reset: calxedaxgmac: add reset function registration

On 10/22/2015 02:09 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 13:54:42 Eric Auger wrote: >> On 10/22/2015 12:13 PM, Arnd Bergmann wrote: >>> On Thursday 22 October 2015 11:41:59 Eric Auger wrote: This patch adds the reset function registration/unregistration.

Re: [Qemu-devel] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC

On Wed, Oct 21, 2015 at 01:20:27PM -0600, Alex Williamson wrote: > The trouble here is that the VF needs to be unplugged prior to the start > of migration because we can't do effective dirty page tracking while the > device is connected and doing DMA. That's exactly what patch 12/12 is trying to

Re: [RFC Patch 09/12] IXGBEVF: Add live migration support for VF driver

On Thu, Oct 22, 2015 at 12:37:41AM +0800, Lan Tianyu wrote: > To let VF driver in the guest to know migration status, Qemu will > fake PCI configure reg 0xF0 and 0xF1 to show migrate status and > get ack from VF driver. I guess this works for current devices but not using 0xF0/0xF1 registers is

Re: [RFC Patch 08/12] IXGBEVF: Rework code of finding the end transmit desc of package

On Thu, Oct 22, 2015 at 12:37:40AM +0800, Lan Tianyu wrote: > When transmit a package, the end transmit desc of package > indicates whether package is sent already. Current code records > the end desc's pointer in the next_to_watch of struct tx buffer. > This code will be broken if shifting desc

Re: [PATCH 14/23] userfaultfd: wake pending userfaults

On Thu, Oct 22, 2015 at 02:10:56PM +0200, Peter Zijlstra wrote: > On Thu, May 14, 2015 at 07:31:11PM +0200, Andrea Arcangeli wrote: > > @@ -255,21 +259,23 @@ int handle_userfault(struct vm_area_struct *vma, > > unsigned long address, > > * through poll/read(). > > */ > >

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On 10/22/2015 12:29 PM, Arnd Bergmann wrote: > On Thursday 22 October 2015 11:42:02 Eric Auger wrote: >> Currently reset lookup is done on probe. This introduces a >> race with new registration mechanism in the case where the >> vfio-platform driver is bound to the device before its module >> is

Re: [PATCH net-next RFC 2/2] vhost_net: basic polling support

On 10/22/2015 02:33 AM, Michael S. Tsirkin wrote: On Thu, Oct 22, 2015 at 01:27:29AM -0400, Jason Wang wrote: This patch tries to poll for new added tx buffer for a while at the end of tx processing. The maximum time spent on polling were limited through a module parameter. To avoid block rx,

Re: [PATCH v2 6/6] vfio: platform: move get/put reset at open/release

On Thu, 2015-10-22 at 16:23 +0200, Eric Auger wrote: > On 10/22/2015 04:10 PM, Arnd Bergmann wrote: > > On Thursday 22 October 2015 15:26:55 Eric Auger wrote: > @@ -181,6 +182,8 @@ static int vfio_platform_open(void *device_data) > if (ret) >

Re: [Qemu-devel] [RFC Patch 06/12] IXGBEVF: Add self emulation layer

On 10/22/2015 05:50 AM, Michael S. Tsirkin wrote: On Wed, Oct 21, 2015 at 01:58:19PM -0700, Alexander Duyck wrote: On 10/21/2015 09:37 AM, Lan Tianyu wrote: In order to restore VF function after migration, add self emulation layer to record regs' values during accessing regs. Signed-off-by:

Re: [PATCH 14/23] userfaultfd: wake pending userfaults

On Thu, Oct 22, 2015 at 04:18:31PM +0200, Andrea Arcangeli wrote: > The risk of memory corruption is still zero no matter what happens > here, in the extremely rare case the app will get a SIGBUS or a That might still upset people, SIGBUS isn't something an app can really recover from. > I'm

Re: [PATCH 14/23] userfaultfd: wake pending userfaults

On Thu, Oct 22, 2015 at 05:15:09PM +0200, Peter Zijlstra wrote: > Indefinitely is such a long time, we should try and finish > computation before the computer dies etc. :-) Indefinitely as read_seqcount_retry, eventually it makes progress. Even returning 0 from the page fault can trigger it

RE: [PATCH v3 08/16] KVM: arm64: handle ITS related GICv3 redistributor registers

Hello! During my work on live migration i found a big bug in your implementation. > -Original Message- > From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf > Of Andre Przywara > Sent: Wednesday, October 07, 2015 5:55 PM > To: marc.zyng...@arm.com;

Re: [PATCH v3 9/9] kvm/x86: Hyper-V kvm exit

On 22/10/2015 18:10, Andrey Smetanin wrote: > A new vcpu exit is introduced to notify the userspace of the > changes in Hyper-V SynIC configuration triggered by guest writing to the > corresponding MSRs. > > Changes v3: > * added KVM_EXIT_HYPERV types and structs notes into docs Thanks. The

RE: [PATCH v3 08/16] KVM: arm64: handle ITS related GICv3 redistributor registers

Hello! One more idea... > Here you store lpis_enabled globally, and this is plain wrong. By the way, may be we should move this flag, together with pendbaser array, into struct vgic_cpu? Then we would not have to allocate them manually. Kind regards, Pavel Fedin Expert Engineer Samsung

Re: [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC

On Wed, Oct 21, 2015 at 10:20 PM, Alex Williamson wrote: > This is why the typical VF agnostic approach here is to using bonding > and fail over to a emulated device during migration, so performance > suffers, but downtime is something acceptable. bonding in the VM

Re: [PATCH net-next RFC 2/2] vhost_net: basic polling support

On Thu, Oct 22, 2015 at 08:46:33AM -0700, Rick Jones wrote: > On 10/22/2015 02:33 AM, Michael S. Tsirkin wrote: > >On Thu, Oct 22, 2015 at 01:27:29AM -0400, Jason Wang wrote: > >>This patch tries to poll for new added tx buffer for a while at the > >>end of tx processing. The maximum time spent on

[PATCH 3/3] kvmtool/run: do not overwrite /virt/init

To me kvm_setup_guest_init() behaviour looks "obviously wrong" and unfriendly because it always overwrites /virt/init. kvm_setup_guest_init() is also called when we are going to use this tree as a rootfs, and without another patch ("kvmtool/run: append cfg.kernel_cmdline at the end of

[PATCH 0/3] kvmtool: don't overwrite /virt/init

Hello, On top of "[PATCH 0/3] kvmtool: tiny init fox x86_64" I sent. I simply can't understand why kvmtool always overwrites /virt/init. This doesn't look right, especially because you can't pass "init=" kernel argument without another patch "[PATCH] kvmtool/run: append cfg.kernel_cmdline at the

[PATCH 2/3] kvmtool/run: don't abuse "root=" parameter, don't pass "rw" to v9fs_mount()

1. kvm_cmd_run_init() appends "root=/dev/root" to real_cmdline if cfg.using_rootfs == T. This doesn't hurt but makes no sense and looks confusing. We do not need to initialiaze the kernel's saved_root_name[] and "/dev/root" means nothing to name_to_dev_t(). We only need to pass

[PATCH 1/3] kvmtool: add lkvm-static to gitignore

add lkvm-static to gitignore Signed-off-by: Oleg Nesterov --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 697a63f..a16a97f 100644 --- a/.gitignore +++ b/.gitignore @@ -1,4 +1,5 @@ /lkvm +/lkvm-static /vm *.o *.d -- 2.4.3 --

Re: [PATCH 0/3] kvmtool: tiny init fox x86_64

Hi Pekka, On 10/22, Pekka Enberg wrote: > > The series looks good to me: > > Acked-by: Pekka Enberg Thanks! I'll try to send some cleanups later. But let me send another simple series first. Oleg. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the

Re: [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC

On Thu, 2015-10-22 at 18:58 +0300, Or Gerlitz wrote: > On Wed, Oct 21, 2015 at 10:20 PM, Alex Williamson > wrote: > > > This is why the typical VF agnostic approach here is to using bonding > > and fail over to a emulated device during migration, so performance > >

[PATCH v3 8/9] kvm/x86: Hyper-V synthetic interrupt controller

SynIC (synthetic interrupt controller) is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest

[PATCH v3 9/9] kvm/x86: Hyper-V kvm exit

A new vcpu exit is introduced to notify the userspace of the changes in Hyper-V SynIC configuration triggered by guest writing to the corresponding MSRs. Changes v3: * added KVM_EXIT_HYPERV types and structs notes into docs Signed-off-by: Andrey Smetanin Reviewed-by:

[GIT PULL] KVM changes for 4.3-rc7

Linus, The following changes since commit b10d92a54dac25a6152f1aa1ffc95c12908035ce: KVM: x86: fix RSM into 64-bit protected mode (2015-10-14 16:39:52 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus for you to fetch changes up to