[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZB4WglXwnOe7HFb1@google.com>
Date: Fri, 24 Mar 2023 14:30:42 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Mingwei Zhang <mizhang@...gle.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, linux-kselftest@...r.kernel.org,
Jim Mattson <jmattson@...gle.com>,
Venkatesh Srinivas <venkateshs@...gle.com>,
Aaron Lewis <aaronlewis@...gle.com>,
"Chang S. Bae" <chang.seok.bae@...el.com>,
Chao Gao <chao.gao@...el.com>
Subject: Re: [PATCH v3 00/13] Overhauling amx_test
On Fri, Mar 24, 2023, Sean Christopherson wrote:
> On Fri, Mar 24, 2023, Sean Christopherson wrote:
> > On Tue, 21 Feb 2023 16:36:42 +0000, Mingwei Zhang wrote:
> > > In this version, I have integrated Aaron's changes to the amx_test. In
> > > addition, we also integrated one fix patch for a kernel warning due to
> > > xsave address issue.
> > >
> > > Patch 1:
> > > Fix a host FPU kernel warning due to missing XTILEDATA in xinit.
> > >
> > > [...]
> >
> > Applied everything except patch 7 to kvm-x86 selftests. Please holler if I
> > missed something subtle about patch 7 (using & vs. ==). This is at the head
> > of kvm-x86/selftests, i.e. I can fix it up if necessary.
> >
> > [01/13] x86/fpu/xstate: Avoid getting xstate address of init_fpstate if fpstate contains the component
> > (no commit info)
>
> *sigh* And by "everything" I meant "all of the selftests patches".
Continuing my circus of goofs, I already force pushed selftests due to an unrelated
mixup. New hashes below (the comment above still stands in case another overwrite
is necessary).
[1/11] KVM: selftests: Add a fully functional "struct xstate" for x86
https://github.com/kvm-x86/linux/commit/5de4a3765b7e
[2/11] KVM: selftests: Fix an error in comment of amx_test
https://github.com/kvm-x86/linux/commit/bec357a4af55
[3/11] KVM: selftests: Enable checking on xcomp_bv in amx_test
https://github.com/kvm-x86/linux/commit/48ad4222c43c
[4/11] KVM: selftests: Add check of CR0.TS in the #NM handler in amx_test
https://github.com/kvm-x86/linux/commit/0aeb9729486a
[5/11] KVM: selftests: Assert that XTILE_DATA is set in IA32_XFD on #NM
https://github.com/kvm-x86/linux/commit/9cbd9aaa670f
[6/11] KVM: selftests: Verify XTILE_DATA in XSTATE isn't affected by IA32_XFD
https://github.com/kvm-x86/linux/commit/bfc5afc37c9d
[7/11] KVM: selftests: Assert that XTILE is XSAVE-enabled
https://github.com/kvm-x86/linux/commit/7e1075f05078
[8/11] KVM: selftests: Assert that both XTILE{CFG,DATA} are XSAVE-enabled
https://github.com/kvm-x86/linux/commit/2ab3991b0b9b
[9/11] KVM: selftests: Move XSAVE and OSXSAVE CPUID checks into AMX's init_regs()
https://github.com/kvm-x86/linux/commit/d01d4a4f7bd2
[10/11] KVM: selftests: Check that the palette table exists before using it
https://github.com/kvm-x86/linux/commit/d32fb0714293
[11/11] KVM: selftests: Check that XTILEDATA supports XFD
https://github.com/kvm-x86/linux/commit/d563164eaeb1
Powered by blists - more mailing lists