> Print the features in a dedicated "vmx flags" line to avoid polluting > the common "flags" and to avoid having to prefix all flags with "vmx_", > which results in horrendously long names. > Pin Control's INTR and NMI exiting are fundamental pillars of VMX, if > they are not supported then the CPU is broken, it does not actually > support VMX, or the kernel wasn't built with support for the target CPU. Don't > print VMX flags if no bits are set in word 0, which holds Pin Controls. > Add support for generating VMX feature names in capflags.c and use the > resulting x86_vmx_flags to print the VMX flags in /proc/cpuinfo. On Wed, at 05:40:08PM -0800, Sean Christopherson wrote: Synthetic flags will be consolidated in a future patch to futherĪrch/x86/kernel/cpu/mkcapflags.sh | 15 +++++++++++-Īrch/x86/kernel/cpu/proc.c | 15 +++++++++++++++Ĥ files changed, 30 insertions(+), 6 deletions(-)īorislav Petkov Dec. The vendor specific code that populates the This means that "flags" and "vmx flags" will haveĭuplicate entries for tpr_shadow (virtual_tpr), vnmi (virtual_nmis),Įpt, flexpriority, vpid and ept_ad, but caps the pollution of "flags" at Keep synthetic VMX flags in cpufeatures to preserve /proc/cpuinfo's ABIįor those flags. Which results in horrendously long names. The common "flags" and to avoid having to prefix all flags with "vmx_", Print the features in a dedicated "vmx flags" line to avoid polluting Support VMX, or the kernel wasn't built with support for the target CPU. They are not supported then the CPU is broken, it does not actually Pin Control's INTR and NMI exiting are fundamental pillars of VMX, if Print VMX flags if no bits are set in word 0, which holds Pin Controls. Resulting x86_vmx_flags to print the VMX flags in /proc/cpuinfo. UTCĪdd support for generating VMX feature names in capflags.c and use the KVM: VMX: Allow KVM_INTEL when building for Centaur and/or Zhaoxin CPUs perf/x86: Provide stubs of KVM helpers for non-Intel CPUs KVM: VMX: Use VMX_FEATURE_* flags to define VMCS control bits KVM: VMX: Check for full VMX support when verifying CPU compatibility KVM: VMX: Use VMX feature flag to query BIOS enabling KVM: VMX: Drop initialization of IA32_FEAT_CTL MSR x86/cpufeatures: Add flag to track whether MSR IA32_FEAT_CTL is configured x86/cpu: Set synthetic VMX cpufeatures during init_ia32_feat_ctl() x86/cpu: Print VMX flags in /proc/cpuinfo using VMX_FEATURES_* x86/cpu: Detect VMX features on Intel, Centaur and Zhaoxin CPUs x86/cpu: Clear VMX feature flag if VMX is not fully enabled x86/zhaoxin: Use common IA32_FEAT_CTL MSR initialization x86/centaur: Use common IA32_FEAT_CTL MSR initialization x86/mce: WARN once if IA32_FEAT_CTL MSR is left unlocked x86/intel: Initialize IA32_FEAT_CTL MSR at boot tools arch x86: Sync msr-index.h from kernel sources selftests: kvm: Replace manual MSR defs with common msr-index.h x86/msr-index: Clean up bit defines for IA32_FEATURE_CONTROL MSR x86/cpu: Clean up handling of VMX features X-Mailing-List: Clean up handling of VMX features Subject: x86/cpu: Print VMX flags in /proc/cpuinfo using Received: from orsmga002.jf. ()īy orsmga101.jf. with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384 X-Amp-Result: SKIPPED(no attachment in message) Received: from ( )īy (Postfix) with ESMTP id 3925A215F1 Received: from (īy (Postfix) with ESMTP id 4FE9D14DB
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |