diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2021-07-30 14:26:24 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-08-03 06:16:40 -0400 |
| commit | 4e62aa96d6e55c1b2a4e841f1f8601eae81e81ae (patch) | |
| tree | e7fde0f3c3d99e2c8f032f2642ceb2c079b3657c /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | f5714bbb5b3120b33dfbf3d81ffc0b98ae4cd4c1 (diff) | |
| download | linux-4e62aa96d6e55c1b2a4e841f1f8601eae81e81ae.tar.gz linux-4e62aa96d6e55c1b2a4e841f1f8601eae81e81ae.tar.bz2 linux-4e62aa96d6e55c1b2a4e841f1f8601eae81e81ae.zip | |
KVM: x86: hyper-v: Check if guest is allowed to use XMM registers for hypercall input
TLFS states that "Availability of the XMM fast hypercall interface is
indicated via the “Hypervisor Feature Identification” CPUID Leaf
(0x40000003, see section 2.4.4) ... Any attempt to use this interface
when the hypervisor does not indicate availability will result in a #UD
fault."
Implement the check for 'strict' mode (KVM_CAP_HYPERV_ENFORCE_CPUID).
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Siddharth Chandrasekaran <sidcha@amazon.de>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20210730122625.112848-4-vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions