mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-27 14:43:58 +08:00
4180bf1b65
Using hypercall to send IPIs by one vmexit instead of one by one for
xAPIC/x2APIC physical mode and one vmexit per-cluster for x2APIC cluster
mode. Intel guest can enter x2apic cluster mode when interrupt remmaping
is enabled in qemu, however, latest AMD EPYC still just supports xapic
mode which can get great improvement by Exit-less IPIs. This patchset
lets a guest send multicast IPIs, with at most 128 destinations per
hypercall in 64-bit mode and 64 vCPUs per hypercall in 32-bit mode.
Hardware: Xeon Skylake 2.5GHz, 2 sockets, 40 cores, 80 threads, the VM
is 80 vCPUs, IPI microbenchmark(https://lkml.org/lkml/2017/12/19/141):
x2apic cluster mode, vanilla
Dry-run: 0, 2392199 ns
Self-IPI: 6907514, 15027589 ns
Normal IPI: 223910476, 251301666 ns
Broadcast IPI: 0, 9282161150 ns
Broadcast lock: 0, 8812934104 ns
x2apic cluster mode, pv-ipi
Dry-run: 0, 2449341 ns
Self-IPI: 6720360, 15028732 ns
Normal IPI: 228643307, 255708477 ns
Broadcast IPI: 0, 7572293590 ns => 22% performance boost
Broadcast lock: 0, 8316124651 ns
x2apic physical mode, vanilla
Dry-run: 0, 3135933 ns
Self-IPI: 8572670, 17901757 ns
Normal IPI: 226444334, 255421709 ns
Broadcast IPI: 0, 19845070887 ns
Broadcast lock: 0, 19827383656 ns
x2apic physical mode, pv-ipi
Dry-run: 0, 2446381 ns
Self-IPI: 6788217, 15021056 ns
Normal IPI: 219454441, 249583458 ns
Broadcast IPI: 0, 7806540019 ns => 154% performance boost
Broadcast lock: 0, 9143618799 ns
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Radim Krčmář <rkrcmar@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
84 lines
4.7 KiB
Plaintext
84 lines
4.7 KiB
Plaintext
KVM CPUID bits
|
|
Glauber Costa <glommer@redhat.com>, Red Hat Inc, 2010
|
|
=====================================================
|
|
|
|
A guest running on a kvm host, can check some of its features using
|
|
cpuid. This is not always guaranteed to work, since userspace can
|
|
mask-out some, or even all KVM-related cpuid features before launching
|
|
a guest.
|
|
|
|
KVM cpuid functions are:
|
|
|
|
function: KVM_CPUID_SIGNATURE (0x40000000)
|
|
returns : eax = 0x40000001,
|
|
ebx = 0x4b4d564b,
|
|
ecx = 0x564b4d56,
|
|
edx = 0x4d.
|
|
Note that this value in ebx, ecx and edx corresponds to the string "KVMKVMKVM".
|
|
The value in eax corresponds to the maximum cpuid function present in this leaf,
|
|
and will be updated if more functions are added in the future.
|
|
Note also that old hosts set eax value to 0x0. This should
|
|
be interpreted as if the value was 0x40000001.
|
|
This function queries the presence of KVM cpuid leafs.
|
|
|
|
|
|
function: define KVM_CPUID_FEATURES (0x40000001)
|
|
returns : ebx, ecx
|
|
eax = an OR'ed group of (1 << flag), where each flags is:
|
|
|
|
|
|
flag || value || meaning
|
|
=============================================================================
|
|
KVM_FEATURE_CLOCKSOURCE || 0 || kvmclock available at msrs
|
|
|| || 0x11 and 0x12.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_NOP_IO_DELAY || 1 || not necessary to perform delays
|
|
|| || on PIO operations.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_MMU_OP || 2 || deprecated.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_CLOCKSOURCE2 || 3 || kvmclock available at msrs
|
|
|| || 0x4b564d00 and 0x4b564d01
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_ASYNC_PF || 4 || async pf can be enabled by
|
|
|| || writing to msr 0x4b564d02
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_STEAL_TIME || 5 || steal time can be enabled by
|
|
|| || writing to msr 0x4b564d03.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_PV_EOI || 6 || paravirtualized end of interrupt
|
|
|| || handler can be enabled by writing
|
|
|| || to msr 0x4b564d04.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_PV_UNHALT || 7 || guest checks this feature bit
|
|
|| || before enabling paravirtualized
|
|
|| || spinlock support.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_PV_TLB_FLUSH || 9 || guest checks this feature bit
|
|
|| || before enabling paravirtualized
|
|
|| || tlb flush.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_ASYNC_PF_VMEXIT || 10 || paravirtualized async PF VM exit
|
|
|| || can be enabled by setting bit 2
|
|
|| || when writing to msr 0x4b564d02
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_PV_SEND_IPI || 11 || guest checks this feature bit
|
|
|| || before using paravirtualized
|
|
|| || send IPIs.
|
|
------------------------------------------------------------------------------
|
|
KVM_FEATURE_CLOCKSOURCE_STABLE_BIT || 24 || host will warn if no guest-side
|
|
|| || per-cpu warps are expected in
|
|
|| || kvmclock.
|
|
------------------------------------------------------------------------------
|
|
|
|
edx = an OR'ed group of (1 << flag), where each flags is:
|
|
|
|
|
|
flag || value || meaning
|
|
==================================================================================
|
|
KVM_HINTS_REALTIME || 0 || guest checks this feature bit to
|
|
|| || determine that vCPUs are never
|
|
|| || preempted for an unlimited time,
|
|
|| || allowing optimizations
|
|
----------------------------------------------------------------------------------
|