On 07/06/2009 05:34 PM, Dong, Eddie wrote:
Avi Kivity wrote:
On 07/06/2009 04:42 PM, Dong, Eddie wrote:
EOI is one of key VM Exit at high bandwidth IO such as VT-d
with 10Gb/s NIC. This patch accelerate guest EOI emulation
utilizing HW VM Exit information.
Won't this fail if the guest uses STOSD to issue the EOI?
Good catch, should we use an exclusion list for the opcode?
That means fetching the opcode and doing partial decoding, which will
negate the advantage.
Or use decode cache for hot IP (RO in EPT for gip)?
How can you tell if the code did not change?
I think it's reasonable to assume that the guest won't use STOSD for EOI
though, and to apply your patch. There's no risk to the host.
We noticed huge amount of vEOI in 10Gb/s NIC which is ~70KHZ for EOI.
With SR-IOV, it could go up much more to even million level. Decode and
emulation cost 7K cycles, while short path may only spend 3-4K cycles.
Yes, and I think we can drop the short path further to almost zero by
using paravirtualization. It would work for Linux and Windows x86 (with
something similar to tpr patching). Unfortunately it won't work on
Windows x64 since it doesn't allow patching.
We can also expose x2apic (already merged) or Hyper-V enlightenment
which converts EOI to MSR write which is fairly fast.
--
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
