status of reducing context switching overhead in KVM

Hi, Rik I saw your presentation at last year 2013 kvm submit. (http://www.linux-kvm.org/wiki/images/2/27/Kvm-forum-2013-idle-latency.pdf). You said there will have some patches later, but I didn't find them. Are you continuing to do the optimization work? Any updates? :-) Many thanks. Thx, Xuekun

Re: status of reducing context switching overhead in KVM

Thanks, Rik On Sat, Jun 21, 2014 at 8:58 PM, Rik van Riel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/21/2014 04:55 AM, Xuekun Hu wrote: >> Hi, Rik >> >> I saw your presentation at last year 2013 kvm submit. >> (http://www.linux-kvm

Re: status of reducing context switching overhead in KVM

Yes, I would like to test. :-) On Mon, Jun 23, 2014 at 3:08 PM, Michael S. Tsirkin wrote: > On Mon, Jun 23, 2014 at 10:08:02AM +0300, Michael S. Tsirkin wrote: >> On Mon, Jun 23, 2014 at 09:18:33AM +0800, Xuekun Hu wrote: >> > Thanks, Rik >> > >> > >>

no handler for some reasons to cause vmexit

Hi, All For some reasons to cause vmexit (e.g. LGDT, INVPCID etc), there is no corresponding handler in kvm. So in general, what will the kvm hypervisor do? Do nothing, and reschedule for next time vmentry? From guest view, no state changed, right? Many thanks. Thx, Xuekun -- To unsubscribe from

kvm perf question

Hi, All I started a VM, and nothing running in that VM. Then using “perf stat” to collect some data, interesting thing is the number of “kvm_apic” is greater than that of “kvm_exit”. My understanding is “kvm:kvm_exit” is the number of vmexit, while “kvm_apic” is the number of vmexit due to apic ac

Does KVM support Intel FlexMigration feature?

Hi, All Does KVM support Intel FlexMigration feature? If yes, is there a doc to describe how to do use it (set cpu features mask)? Many thanks. Thx, Xuekun -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info a

qemu/kvm has limited pci config space exposed to guest device driver to access

Hi, All I found qemu/kvm has limited pci config space exposed to guest device driver to access. I’m wondering is there any reason why not expose the whole pci config space to guest, since some kind of devices has special register in that area. Many thanks. Thx, Xuekun -- To unsubscribe from this

Re: qemu/kvm has limited pci config space exposed to guest device driver to access

13, 2013 at 10:55 AM, Alex Williamson wrote: > On Fri, 2013-12-13 at 10:34 +0800, Xuekun Hu wrote: >> Hi, All >> >> I found qemu/kvm has limited pci config space exposed to guest device >> driver to access. I’m wondering is there any reason why not expose the >>

lat_rpc performance issue in kvm?

Hi, All I’m using lat_rpc (one workload in LMBench) to measure the inter-process communication latency between two processes (client/server program). In linux guest in KVM, if binding the client and server apps to separate cores, the latency is much worse than that binding the client and server ap

the number of PCI pass-through devices limit?

Hi, All Is there a limit for number of PCI pass-through devices in KVM? For Legacy PCI device assignement or VFIO pass-through method? Many thanks. Thx, Xuekun -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo in