diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2023-12-05 11:36:15 +0100 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2023-12-07 09:33:42 -0800 |
| commit | 87562052c965ba7de6dc490434e53691fe46c898 (patch) | |
| tree | 8251478a3977d465043b4f08fabd3b72876fd8f0 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 0277022a77a56f8251e8cf8d25e9308478e79ea5 (diff) | |
KVM: x86/xen: Remove unneeded xen context from kvm_arch when !CONFIG_KVM_XEN
Saving a few bytes of memory per KVM VM is certainly great but what's more
important is the ability to see where the code accesses Xen emulation
context while CONFIG_KVM_XEN is not enabled. Currently, kvm_cpu_get_extint()
is the only such place and it is harmless: kvm_xen_has_interrupt() always
returns '0' when !CONFIG_KVM_XEN.
No functional change intended.
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Tested-by: Jeremi Piotrowski <jpiotrowski@linux.microsoft.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Link: https://lore.kernel.org/r/20231205103630.1391318-2-vkuznets@redhat.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions