From: David Vrabel <david.vrabel@citrix.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: <lguest@lists.ozlabs.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
David Vrabel <david.vrabel@citrix.com>,
Thomas Gleixner <tglx@linutronix.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH] x86/cpu: Fix SMAP check in PVOPS environments
Date: Fri, 5 Jun 2015 10:33:14 +0100 [thread overview]
Message-ID: <55716CDA.4020007@citrix.com> (raw)
In-Reply-To: <87lhfyuaiu.fsf@rustcorp.com.au>
On 05/06/15 03:58, Rusty Russell wrote:
>
> Subject: x86: rename save_fl/restore_fl paravirt ops to highlight eflags.
> From: Rusty Russell <rusty@rustcorp.com.au>
>
> As the comment in arch/x86/include/asm/paravirt_types.h says:
>
> * Get/set interrupt state. save_fl and restore_fl are only
> * expected to use X86_EFLAGS_IF; all other bits
> * returned from save_fl are undefined, and may be ignored by
> * restore_fl.
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
[...]
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -1074,8 +1074,8 @@ void xen_setup_vcpu_info_placement(void)
> * percpu area for all cpus, so make use of it. Note that for
> * PVH we want to use native IRQ mechanism. */
> if (have_vcpu_info_placement && !xen_pvh_domain()) {
> - pv_irq_ops.save_fl = __PV_IS_CALLEE_SAVE(xen_save_fl_direct);
> - pv_irq_ops.restore_fl = __PV_IS_CALLEE_SAVE(xen_restore_fl_direct);
> + pv_irq_ops.save_eflags_if = __PV_IS_CALLEE_SAVE(xen_save_fl_direct);
> + pv_irq_ops.restore_eflags_if = __PV_IS_CALLEE_SAVE(xen_restore_fl_direct);
> pv_irq_ops.irq_disable = __PV_IS_CALLEE_SAVE(xen_irq_disable_direct);
> pv_irq_ops.irq_enable = __PV_IS_CALLEE_SAVE(xen_irq_enable_direct);
> pv_mmu_ops.read_cr2 = xen_read_cr2_direct;
> @@ -1102,8 +1102,8 @@ static unsigned xen_patch(u8 type, u16 clobbers, void *insnbuf,
> switch (type) {
> SITE(pv_irq_ops, irq_enable);
> SITE(pv_irq_ops, irq_disable);
> - SITE(pv_irq_ops, save_fl);
> - SITE(pv_irq_ops, restore_fl);
> + SITE(pv_irq_ops, save_eflags_if);
> + SITE(pv_irq_ops, restore_eflags_if);
> #undef SITE
>
> patch_site:
> diff --git a/arch/x86/xen/irq.c b/arch/x86/xen/irq.c
Acked-by: David Vrabel <david.vrabel@citrix.com>
Thanks.
David
next prev parent reply other threads:[~2015-06-05 9:33 UTC|newest]
Thread overview: 10+ 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 20:29 ` H. Peter Anvin
2015-06-05 2:58 ` Rusty Russell
2015-06-05 7:13 ` Ingo Molnar
2015-06-05 9:33 ` David Vrabel [this message]
2015-11-17 14:59 ` Andrew Cooper
2015-11-19 10:12 ` [tip:x86/urgent] " tip-bot for 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=55716CDA.4020007@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.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 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).