From: Mingwei Zhang <mizhang@google.com>
To: Sean Christopherson <seanjc@google.com>,
Aaron Lewis <aaronlewis@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, jmattson@google.com,
seanjc@google.com
Subject: Re: [PATCH v3 0/8] Clean up the supported xfeatures
Date: Mon, 20 Mar 2023 15:45:51 +0000 [thread overview]
Message-ID: <ZBh/r7CzBRv5qtr8@google.com> (raw)
In-Reply-To: <20230224223607.1580880-1-aaronlewis@google.com>
On Fri, Feb 24, 2023, Aaron Lewis wrote:
> Make sure the supported xfeatures, i.e. EDX:EAX of CPUID.(EAX=0DH,ECX=0),
> for MPX, AVX-512, and AMX are in a valid state and follow the rules
> outlined in the SDM vol 1, section 13.3 ENABLING THE XSAVE FEATURE SET
> AND XSAVE-ENABLED FEATURES. While those rules apply to the enabled
> xfeatures, i.e. XCR0, use them to set the supported xfeatures. That way
> if they are used by userspace or a guest to set the enabled xfeatures,
> they won't cause a #GP.
>
> A test is then added to verify the supported xfeatures are in this
> sanitied state.
>
> v2 -> v3:
> - Sanitize the supported XCR0 in XSAVES2 [Sean]
> - Split AVX-512 into 2 commits [Sean]
> - Added XFEATURE_MASK_FP to selftests [Sean]
> - Reworked XCR0 test to split up architectural and kvm rules [Sean]
>
> Aaron Lewis (8):
> KVM: x86: Add kvm_permitted_xcr0()
> KVM: x86: Clear all supported MPX xfeatures if they are not all set
> KVM: x86: Clear all supported AVX-512 xfeatures if they are not all set
> KVM: x86: Clear AVX-512 xfeatures if SSE or AVX is clear
> KVM: x86: Clear all supported AMX xfeatures if they are not all set
> KVM: selftests: Hoist XGETBV and XSETBV to make them more accessible
> KVM: selftests: Add XFEATURE masks to common code
> KVM: selftests: Add XCR0 Test
>
> arch/x86/kvm/cpuid.c | 27 +++-
> arch/x86/kvm/cpuid.h | 1 +
> arch/x86/kvm/x86.c | 4 +-
> tools/testing/selftests/kvm/Makefile | 1 +
> .../selftests/kvm/include/x86_64/processor.h | 52 +++++++
> tools/testing/selftests/kvm/x86_64/amx_test.c | 46 ++-----
> .../selftests/kvm/x86_64/xcr0_cpuid_test.c | 128 ++++++++++++++++++
> 7 files changed, 220 insertions(+), 39 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/x86_64/xcr0_cpuid_test.c
>
ping? This series has been soaked for a while. Sean, would you mind
taking another look?
next prev parent reply other threads:[~2023-03-20 15:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 22:35 [PATCH v3 0/8] Clean up the supported xfeatures Aaron Lewis
2023-02-24 22:36 ` [PATCH v3 1/8] KVM: x86: Add kvm_permitted_xcr0() Aaron Lewis
2023-03-03 21:13 ` Mingwei Zhang
2023-02-24 22:36 ` [PATCH v3 2/8] KVM: x86: Clear all supported MPX xfeatures if they are not all set Aaron Lewis
2023-03-03 21:23 ` Mingwei Zhang
2023-03-03 22:23 ` Aaron Lewis
2023-03-07 16:32 ` Mingwei Zhang
2023-03-23 20:29 ` Sean Christopherson
2023-03-23 21:10 ` Mingwei Zhang
2023-03-23 21:16 ` Mingwei Zhang
2023-03-23 21:30 ` Sean Christopherson
2023-03-23 21:29 ` Sean Christopherson
2023-02-24 22:36 ` [PATCH v3 3/8] KVM: x86: Clear all supported AVX-512 " Aaron Lewis
2023-02-24 22:36 ` [PATCH v3 4/8] KVM: x86: Clear AVX-512 xfeatures if SSE or AVX is clear Aaron Lewis
2023-02-24 22:36 ` [PATCH v3 5/8] KVM: x86: Clear all supported AMX xfeatures if they are not all set Aaron Lewis
2023-03-03 21:12 ` Mingwei Zhang
2023-02-24 22:36 ` [PATCH v3 6/8] KVM: selftests: Hoist XGETBV and XSETBV to make them more accessible Aaron Lewis
2023-03-03 21:24 ` Mingwei Zhang
2023-02-24 22:36 ` [PATCH v3 7/8] KVM: selftests: Add XFEATURE masks to common code Aaron Lewis
2023-03-03 21:16 ` Mingwei Zhang
2023-03-03 22:25 ` Aaron Lewis
2023-03-07 16:33 ` Mingwei Zhang
2023-02-24 22:36 ` [PATCH v3 8/8] KVM: selftests: Add XCR0 Test Aaron Lewis
2023-03-02 20:34 ` Mingwei Zhang
2023-03-02 22:50 ` Aaron Lewis
2023-03-03 21:11 ` Mingwei Zhang
2023-03-23 21:46 ` Sean Christopherson
2023-03-20 15:45 ` Mingwei Zhang [this message]
2023-03-23 21:47 ` [PATCH v3 0/8] Clean up the supported xfeatures Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZBh/r7CzBRv5qtr8@google.com \
--to=mizhang@google.com \
--cc=aaronlewis@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).