From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com
Subject: Re: [PATCH v3] x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen
Date: Fri, 5 May 2017 12:02:02 -0400 [thread overview]
Message-ID: <4e6a3981-97c8-c628-03c2-444c06c559d6@oracle.com> (raw)
In-Reply-To: <9c435a66-f8b1-5250-f3bf-cfada84d3d97@suse.com>
On 05/05/2017 01:09 AM, Juergen Gross wrote:
> Any comments?
>
>
> Juergen
>
> On 27/04/17 07:01, Juergen Gross wrote:
>> When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set
>> on AMD cpus.
>>
>> This bug/feature bit is kind of special as it will be used very early
>> when switching threads. Setting the bit and clearing it a little bit
>> later leaves a critical window where things can go wrong. This time
>> window has enlarged a little bit by using setup_clear_cpu_cap() instead
>> of the hypervisor's set_cpu_features callback. It seems this larger
>> window now makes it rather easy to hit the problem.
>>
>> The proper solution is to never set the bit in case of Xen.
FWIW,
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> arch/x86/kernel/cpu/amd.c | 5 +++--
>> arch/x86/xen/enlighten_pv.c | 1 -
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
>> index c36140d788fe..b6da6e75e3a8 100644
>> --- a/arch/x86/kernel/cpu/amd.c
>> +++ b/arch/x86/kernel/cpu/amd.c
>> @@ -799,8 +799,9 @@ static void init_amd(struct cpuinfo_x86 *c)
>> if (cpu_has(c, X86_FEATURE_3DNOW) || cpu_has(c, X86_FEATURE_LM))
>> set_cpu_cap(c, X86_FEATURE_3DNOWPREFETCH);
>>
>> - /* AMD CPUs don't reset SS attributes on SYSRET */
>> - set_cpu_bug(c, X86_BUG_SYSRET_SS_ATTRS);
>> + /* AMD CPUs don't reset SS attributes on SYSRET, Xen does. */
>> + if (!cpu_has(c, X86_FEATURE_XENPV))
>> + set_cpu_bug(c, X86_BUG_SYSRET_SS_ATTRS);
>> }
>>
>> #ifdef CONFIG_X86_32
>> diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
>> index a1af4f68278f..dcfd07faf1c3 100644
>> --- a/arch/x86/xen/enlighten_pv.c
>> +++ b/arch/x86/xen/enlighten_pv.c
>> @@ -290,7 +290,6 @@ static bool __init xen_check_xsave(void)
>>
>> static void __init xen_init_capabilities(void)
>> {
>> - setup_clear_cpu_cap(X86_BUG_SYSRET_SS_ATTRS);
>> setup_force_cpu_cap(X86_FEATURE_XENPV);
>> setup_clear_cpu_cap(X86_FEATURE_DCA);
>> setup_clear_cpu_cap(X86_FEATURE_APERFMPERF);
>>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-05 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170427050120.6894-1-jgross@suse.com>
2017-05-05 5:09 ` [PATCH v3] x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen Juergen Gross
[not found] ` <9c435a66-f8b1-5250-f3bf-cfada84d3d97@suse.com>
2017-05-05 16:02 ` Boris Ostrovsky [this message]
2017-05-11 10:31 ` Juergen Gross
[not found] ` <566478e1-3a1c-2800-8662-09a6ad31a7b6@suse.com>
2017-05-11 12:46 ` Thomas Gleixner
2017-04-27 5:01 Juergen Gross
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=4e6a3981-97c8-c628-03c2-444c06c559d6@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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).