diff options
| author |   Sean Christopherson <seanjc@google.com> | 2024-10-03 16:43:32 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2024-11-01 09:26:32 -0700 |
| commit | 8ae01bf64caaea5562f3af40a2fbe404a1e79403 (patch) | |
| tree | 952612aa21d7f708ecf2051de1cc877852a36348 /scripts/gdb/linux/modules.py | |
| parent | KVM: selftests: Configure XCR0 to max supported value by default (diff) | |
| download | wireguard-linux-8ae01bf64caaea5562f3af40a2fbe404a1e79403.tar.xz wireguard-linux-8ae01bf64caaea5562f3af40a2fbe404a1e79403.zip | |
KVM: selftests: Verify XCR0 can be "downgraded" and "upgraded"
Now that KVM selftests enable all supported XCR0 features by default, add
a testcase to the XCR0 vs. CPUID test to verify that the guest can disable
everything except the legacy FPU in XCR0, and then re-enable the full
feature set, which is kinda sorta what the test did before XCR0 was setup
by default.
Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Link: https://lore.kernel.org/r/20241003234337.273364-7-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions