From: Andrew Cooper <Andrew.Cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Wei Liu" <wl@xen.org>, "Roger Pau Monne" <roger.pau@citrix.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/CPUID: surface suitable value in EBX of XSTATE subleaf 1
Date: Wed, 24 Aug 2022 12:02:23 +0000 [thread overview]
Message-ID: <0a4c3091-cb52-161a-e281-477889f202fe@citrix.com> (raw)
In-Reply-To: <e9de03a3-77cf-bc90-be48-ef6b1f133661@suse.com>
On 23/08/2022 13:01, Jan Beulich wrote:
> On 23.08.2022 12:48, Andrew Cooper wrote:
>> On 23/08/2022 10:27, Jan Beulich wrote:
>>> On 23.08.2022 10:59, Andrew Cooper wrote:
>>>> On 23/08/2022 07:42, Jan Beulich wrote:
>>>>> +++ b/xen/arch/x86/cpuid.c
>>>>> @@ -1142,7 +1142,7 @@ void guest_cpuid(const struct vcpu *v, u
>>>>> switch ( subleaf )
>>>>> {
>>>>> case 1:
>>>>> - if ( p->xstate.xsaves )
>>>>> + if ( p->xstate.xsavec || p->xstate.xsaves )
>>>> If we're doing this, then it wants to be xsavec only, with the comment
>>>> being extended to explain why.
>>> Why would that be? Both insns use compacted format, and neither is
>>> dependent upon the other in terms of being supported. IOW XSAVES alone
>>> and XSAVEC alone enabled for a domain should still lead through this
>>> path.
>> Hmm. Because my fixes to compaction handling haven't been committed
>> yet, and in particular one the one which makes XSAVES strictly depend on
>> XSAVEC.
>>
>> In which case this hunk is correct for Xen as it currently is, and will
>> be need to be adjusted when I rebase the compaction series.
> May I translate this to an Ack then? Iirc there were no other change
> requests.
I was hoping that Marek would have time to test it too, seeing as he
reported the bug first. But seeing as he's busy...
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com> (with the typo in
the commit message fixed.)
~Andrew
next prev parent reply other threads:[~2022-08-24 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 6:42 [PATCH] x86/CPUID: surface suitable value in EBX of XSTATE subleaf 1 Jan Beulich
2022-08-23 8:59 ` Andrew Cooper
2022-08-23 9:27 ` Jan Beulich
2022-08-23 10:48 ` Andrew Cooper
2022-08-23 12:01 ` Jan Beulich
2022-08-24 12:02 ` Andrew Cooper [this message]
2022-08-24 12:11 ` Andrew Cooper
2022-08-24 6:00 ` Jan Beulich
2022-08-24 12:19 ` Andrew Cooper
2022-08-24 12:36 ` Jan Beulich
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=0a4c3091-cb52-161a-e281-477889f202fe@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=tglx@linutronix.de \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.