From: Sean Christopherson <seanjc@google.com>
To: Christian Ludloff <ludloff@gmail.com>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
jmattson@google.com, pbonzini@redhat.com, kvm@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
zhao1.liu@intel.com
Subject: Re: [PATCH v9 20/20] KVM: selftests: Add APX state handling and XCR0 sanity checks
Date: Thu, 19 Nov 2026 06:46:01 -0800 [thread overview]
Message-ID: <av8LqXyAklPZ2-rD@seanjc-mac.roam.internal> (raw)
In-Reply-To: <CAKSQd8Wcw-DUR_JO9YFw17u691gjNyvySwfhPW_P5P3ik=_tBQ@mail.gmail.com>
On Wed, Nov 18, 2026, Christian Ludloff wrote:
> > Since APX repurposes the XSAVE area previously used by MPX in the
> > non-compacted format, add a check to ensure that MPX state is not set
> > when APX is enabled.
>
> For the sake of completeness...
For the sake of my sanity, fix your mail client to set In-Reply-To properly.
It's not a gmail problem. I don't see this issue with mails from anyone else,
and I just tested that sending a mail through the gmail web interface sets the
header as expected.
> EVO processors do support simultaneously
> enabled MPX and APX, with state that does
> not overlap. (And several MSR control bits.)
Until EVO processors are officially supported in KVM selftests, I don't care. I
am a-ok supporting EVO processors, but if you want upstream to care about them,
then someone needs to take the time to enable support.
next prev parent reply other threads:[~2026-11-19 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 5:56 Christian Ludloff
2026-11-19 14:46 ` Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-17 18:02 [PATCH v9 00/20] KVM: x86: Enable APX for guest Chang S. Bae
2026-11-17 18:03 ` [PATCH v9 20/20] KVM: selftests: Add APX state handling and XCR0 sanity checks Chang S. Bae
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=av8LqXyAklPZ2-rD@seanjc-mac.roam.internal \
--to=seanjc@google.com \
--cc=chang.seok.bae@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=pbonzini@redhat.com \
--cc=x86@kernel.org \
--cc=zhao1.liu@intel.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
all inboxes | Powered by JetHome®