aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorSean Christopherson <sean.j.christopherson@intel.com>2018-11-05 10:44:32 -0800
committerPaolo Bonzini <pbonzini@redhat.com>2018-12-21 11:28:25 +0100
commit9b7ebff23cb8a8e126b3852ad0b1bfb284f25273 (patch)
treea445fe43cf8d3c0fd70705aaf3f58dc2817be16b /tools/perf/scripts/python/export-to-postgresql.py
parentkvm: vmx: Allow guest read access to IA32_TSC (diff)
downloadlinux-dev-9b7ebff23cb8a8e126b3852ad0b1bfb284f25273.tar.xz
linux-dev-9b7ebff23cb8a8e126b3852ad0b1bfb284f25273.zip
KVM: x86: Remove KF() macro placeholder
Although well-intentioned, keeping the KF() definition as a hint for handling scattered CPUID features may be counter-productive. Simply redefining the bit position only works for directly manipulating the guest's CPUID leafs, e.g. it doesn't make guest_cpuid_has() magically work. Taking an alternative approach, e.g. ensuring the bit position is identical between the Linux-defined and hardware-defined features, may be a simpler and/or more effective method of exposing scattered features to the guest. Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions