Re: [v1][KVM][PATCH 1/1] kvm:ppc:booehv: direct ISI exception to Guest

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/11/2013 03:39 AM, Alexander Graf wrote:


Am 10.05.2013 um 21:22 schrieb Scott Wood <scottwood@xxxxxxxxxxxxx>:

On 05/10/2013 12:57:33 PM, Alexander Graf wrote:
Could you guys please collect performance data during the next weeks on both guest-directed ISIs as well as VF MMIOs (preferably with in-kernel MMIO), so that we can decide on the direction that's worth going towards?

Collecting data on VF MMIO would require implementing it (or at least salvaging and fixing some old code), which is not a high priority at the moment.  If we do implement VF in the future we could always undo the direct ISI change, but it would still be nice to know if there's any real benefit in the first place.

Mike sounded like he had an almost working poc, which is good enough to collect rough numbers.

Which can the test case be adopted?

Mike,

If you already have a good case for your poc, please share that with me. Then I'd like to run that.

Tiejun


And yes, changes like these should always get at least basic performance numbers along with them, regardless of drawbacks.


Alex


FWIW, I doubt that the "more stress on HW TLB" will be significant.

-Scott


--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux