From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/xen: fix xsave capability setting
Date: Wed, 26 Apr 2017 09:51:35 -0400 [thread overview]
Message-ID: <7a749fae-4fda-c6ab-d3b0-598a7132e9de@oracle.com> (raw)
In-Reply-To: <20170425064740.1251-1-jgross@suse.com>
On 04/25/2017 02:47 AM, Juergen Gross wrote:
> Commit 690b7f10b4f9f ("x86/xen: use capabilities instead of fake cpuid
> values for xsave") introduced a regression as it tried to make use of
> the fixup feature before it being available.
>
> Fall back to the old variant testing via cpuid().
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Boris Ostrovsky <boris.osrtovsky@oracle.com>
(This, BTW, was apparently broken on Intel as well, at least if you go
back to Xen 4.1).
prev parent reply other threads:[~2017-04-26 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 6:47 [PATCH] x86/xen: fix xsave capability setting Juergen Gross
2017-04-26 13:51 ` Boris Ostrovsky [this message]
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=7a749fae-4fda-c6ab-d3b0-598a7132e9de@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.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 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).