All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	lguest@lists.ozlabs.org, X86 ML <x86@kernel.org>,
	Denys Vlasenko <vda.linux@googlemail.com>
Subject: Re: [PATCH] [RFC] x86/cpu: Fix SMAP check in PVOPS environments
Date: Mon, 20 Apr 2015 17:35:35 -0700	[thread overview]
Message-ID: <55359B57.3070008@kernel.org> (raw)
In-Reply-To: <1429549782-12962-1-git-send-email-andrew.cooper3@citrix.com>

On 04/20/2015 10:09 AM, Andrew Cooper wrote:
> There appears to be no formal statement of what pv_irq_ops.save_fl() is
> supposed to return precisely.  Native returns the full flags, while lguest and
> Xen only return the Interrupt Flag, and both have comments by the
> implementations stating that only the Interrupt Flag is looked at.  This may
> have been true when initially implemented, but no longer is.
>
> To make matters worse, the Xen PVOP leaves the upper bits undefined, making
> the BUG_ON() undefined behaviour.  Experimentally, this now trips for 32bit PV
> guests on Broadwell hardware.  The BUG_ON() is consistent for an individual
> build, but not consistent for all builds.  It has also been a sitting timebomb
> since SMAP support was introduced.
>
> Use native_save_fl() instead, which will obtain an accurate view of the AC
> flag.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: Ingo Molnar <mingo@redhat.com>
> CC: H. Peter Anvin <hpa@zytor.com>
> CC: x86@kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> CC: David Vrabel <david.vrabel@citrix.com>
> CC: xen-devel <xen-devel@lists.xen.org>
> CC: Rusty Russell <rusty@rustcorp.com.au>
> CC: lguest@lists.ozlabs.org
>
> ---
> This patch is RFC because I am not certain that native_save_fl() is
> necessarily the correct solution on lguest, but it does seem that setup_smap()
> wants to check the actual AC bit, rather than an idealised value.
>
> A different approach, given the dual nature of the AC flag now is to gate
> setup_smap() on a kernel rpl of 0.  SMAP necessarily can't be used in a
> paravirtual situation where the kernel runs in cpl > 0.
>
> Another different approach would be to formally state that
> pv_irq_ops.save_fl() needs to return all the flags, which would make
> local_irq_save() safe to use in this circumstance, but that makes a hotpath
> longer for the sake of a single boot time check.

...which reminds me:

Why does native_restore_fl restore anything other than IF?  A branch and 
sti should be considerably faster than popf.

Also, if we did this, could Xen use PVI and then use native_restore_fl 
and avoid lots of pvops?

--Andy

  parent reply	other threads:[~2015-04-21  0:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 17:09 [PATCH] [RFC] x86/cpu: Fix SMAP check in PVOPS environments Andrew Cooper
2015-04-20 17:11 ` David Vrabel
2015-04-20 17:11 ` David Vrabel
2015-04-21  0:35 ` Andy Lutomirski
2015-04-21  0:35 ` Andy Lutomirski [this message]
2015-04-21  5:07   ` Rusty Russell
2015-04-21  5:07   ` Rusty Russell
2015-04-21  8:26   ` Andrew Cooper
2015-04-21  8:26   ` Andrew Cooper
2015-04-21 12:45   ` [RFC PATCH] x86/asm/irq: Don't use POPF but STI Ingo Molnar
2015-04-21 13:09     ` Borislav Petkov
2015-04-21 15:22       ` Ingo Molnar
2015-04-21 15:22       ` Ingo Molnar
2015-04-21 13:09     ` Borislav Petkov
2015-04-21 16:12     ` Linus Torvalds
2015-04-21 22:39       ` Andy Lutomirski
2015-04-21 22:39       ` Andy Lutomirski
2015-04-21 16:12     ` Linus Torvalds
2015-04-21 12:45   ` Ingo Molnar
2015-04-21  8:36 ` [PATCH] [RFC] x86/cpu: Fix SMAP check in PVOPS environments Jan Beulich
2015-04-21  8:36 ` [Xen-devel] " Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2015-04-20 17:09 Andrew Cooper

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=55359B57.3070008@kernel.org \
    --to=luto@kernel.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lguest@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=vda.linux@googlemail.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xen.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.