From: "H. Peter Anvin" <hpa@zytor.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
lguest@lists.ozlabs.org, stable@vger.kernel.org
Subject: Re: [PATCH] x86/cpu: Fix SMAP check in PVOPS environments
Date: Thu, 04 Jun 2015 13:29:19 -0700 [thread overview]
Message-ID: <5570B51F.4060908@zytor.com> (raw)
In-Reply-To: <873827uu2i.fsf@rustcorp.com.au>
On 06/04/2015 12:55 PM, Rusty Russell wrote:
>
> Yeah, hard cases make bad law.
>
> I'm not too unhappy with this fix; ideally we'd rename save_fl and
> restore_fl to save_eflags_if and restore_eflags_if too.
>
I would be fine with this... but please document what the bloody
semantics of pvops is actually supposed to be.
-hpa
next prev parent reply other threads:[~2015-06-04 20:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 9:31 [PATCH] x86/cpu: Fix SMAP check in PVOPS environments Andrew Cooper
2015-06-04 6:38 ` H. Peter Anvin
2015-06-04 8:58 ` Andrew Cooper
2015-06-04 19:55 ` Rusty Russell
2015-06-04 19:55 ` Rusty Russell
2015-06-04 20:29 ` H. Peter Anvin
2015-06-04 20:29 ` H. Peter Anvin [this message]
2015-06-05 2:58 ` Rusty Russell
2015-06-05 2:58 ` Rusty Russell
2015-06-05 7:13 ` Ingo Molnar
2015-06-05 7:13 ` Ingo Molnar
2015-06-05 9:33 ` David Vrabel
2015-06-05 9:33 ` [Xen-devel] " David Vrabel
2015-06-04 8:58 ` Andrew Cooper
2015-06-04 6:38 ` H. Peter Anvin
2015-11-17 14:59 ` Andrew Cooper
2015-11-17 14:59 ` Andrew Cooper
2015-11-19 10:12 ` [tip:x86/urgent] " tip-bot for Andrew Cooper
2015-11-19 10:12 ` tip-bot for Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 9:31 [PATCH] " 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=5570B51F.4060908@zytor.com \
--to=hpa@zytor.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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.