From: Sean Christopherson <seanjc@google.com>
To: Aaron Lewis <aaronlewis@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, jmattson@google.com
Subject: Re: [PATCH v2 1/2] KVM: selftests: Assert that XSAVE supports XTILE in amx_test
Date: Tue, 3 Jan 2023 18:24:27 +0000 [thread overview]
Message-ID: <Y7Ry24zfi1/ZOnf8@google.com> (raw)
In-Reply-To: <Y7RwZg9XGIJREcph@google.com>
On Tue, Jan 03, 2023, Sean Christopherson wrote:
> On Fri, Dec 30, 2022, Aaron Lewis wrote:
> > The check in amx_test that ensures that XSAVE supports XTILE, doesn't
> > actually check anything. It simply returns a bool which the test does
> > nothing with.
> >
> > Assert that XSAVE supports XTILE.
> >
> > Fixes: 5dc19f1c7dd3 ("KVM: selftests: Convert AMX test to use X86_PROPRETY_XXX")
>
> Doh.
>
> > Signed-off-by: Aaron Lewis <aaronlewis@google.com>
> > ---
> > tools/testing/selftests/kvm/x86_64/amx_test.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/kvm/x86_64/amx_test.c b/tools/testing/selftests/kvm/x86_64/amx_test.c
> > index bd72c6eb3b670..2f555f5c93e99 100644
> > --- a/tools/testing/selftests/kvm/x86_64/amx_test.c
> > +++ b/tools/testing/selftests/kvm/x86_64/amx_test.c
> > @@ -119,9 +119,9 @@ static inline void check_cpuid_xsave(void)
> > GUEST_ASSERT(this_cpu_has(X86_FEATURE_OSXSAVE));
> > }
> >
> > -static bool check_xsave_supports_xtile(void)
> > +static inline void check_xsave_supports_xtile(void)
>
> Don't explicitly tag local static functions as inline (ignore the existing code
> that sets a bad precedent), modern compilers don't need the hint to generate
> optimal code,
>
> > {
> > - return __xgetbv(0) & XFEATURE_MASK_XTILE;
> > + GUEST_ASSERT(__xgetbv(0) & XFEATURE_MASK_XTILE);
>
> Any objection to moving the assertion into check_xtile_info() and dropping this
> one-line helper?
Actually, this code is silly, and arguably unnecessary. init_regs() explicitly
sets XCR0 to XFEATURE_MASK_XTILE. If something goes awry, XSETBV should #GP.
If we want to be really paranoid and assert that KVM didn't silently fail XSETBV,
then the more logical place for the assertion is immediately after the XSETBV.
i.e.
static void init_regs(void)
{
uint64_t cr4, xcr0;
/* turn on CR4.OSXSAVE */
cr4 = get_cr4();
cr4 |= X86_CR4_OSXSAVE;
set_cr4(cr4);
xcr0 = __xgetbv(0);
xcr0 |= XFEATURE_MASK_XTILE;
__xsetbv(0x0, xcr0);
GUEST_ASSERT((__xgetbv(0) & XFEATURE_MASK_XTILE) == XFEATURE_MASK_XTILE);
}
next prev parent reply other threads:[~2023-01-03 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 1:36 [PATCH v2 0/2] Fix check in amx_test Aaron Lewis
2022-12-30 1:36 ` [PATCH v2 1/2] KVM: selftests: Assert that XSAVE supports XTILE " Aaron Lewis
2023-01-03 18:13 ` Sean Christopherson
2023-01-03 18:24 ` Sean Christopherson [this message]
2022-12-30 1:36 ` [PATCH v2 2/2] KVM: selftests: Assert that XSAVE supports both XTILE{CFG,DATA} Aaron Lewis
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=Y7Ry24zfi1/ZOnf8@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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