xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Feng Wu <feng.wu@intel.com>, xen-devel@lists.xen.org
Cc: keir.xen@gmail.com, JBeulich@suse.com
Subject: Re: [PATCH 3/3] x86: Use alternative mechanism to define CLAC/STAC
Date: Mon, 26 May 2014 16:49:33 +0100	[thread overview]
Message-ID: <5383628D.4000907@citrix.com> (raw)
In-Reply-To: <1401089273-16425-4-git-send-email-feng.wu@intel.com>

On 26/05/2014 08:27, Feng Wu wrote:
> This patch use alternative mechanism to define CLAC/STAC.
>
> Signed-off-by: Feng Wu <feng.wu@intel.com>
> ---
>  xen/include/asm-x86/asm_defns.h | 36 +++++++++++++++++++++++-------------
>  1 file changed, 23 insertions(+), 13 deletions(-)
>
> diff --git a/xen/include/asm-x86/asm_defns.h b/xen/include/asm-x86/asm_defns.h
> index 87a462f..92024cc 100644
> --- a/xen/include/asm-x86/asm_defns.h
> +++ b/xen/include/asm-x86/asm_defns.h
> @@ -10,6 +10,8 @@
>  #include <asm/percpu.h>
>  #include <xen/stringify.h>
>  #include <asm/cpufeature.h>
> +#include <asm/nops.h>
> +#include <asm/alternative.h>

alternatives should include nops, to avoid needing a double include
everywhere alternative() is used.

>  
>  #ifndef __ASSEMBLY__
>  void ret_from_intr(void);
> @@ -166,26 +168,34 @@ void ret_from_intr(void);
>  #define __ASM_STAC      .byte 0x0f,0x01,0xcb
>  
>  #ifdef __ASSEMBLY__
> -#define ASM_AC(op)                                       \
> -        btl $X86_FEATURE_SMAP & 31,                      \
> -        CPUINFO_FEATURE_OFFSET(X86_FEATURE_SMAP)+boot_cpu_data(%rip); \
> -        jnc 881f;                                        \
> -        __ASM_##op;                                      \
> -881:
> -
> -#define ASM_STAC ASM_AC(STAC)
> -#define ASM_CLAC ASM_AC(CLAC)
> +#define ASM_CLAC                                                       \
> +        661: ASM_NOP3;                                                 \
> +        .pushsection .altinstr_replacement, "ax";                      \

The altinstr_replacement section doesn't need to be executable.  The
data inside it is copied out into the .text section.

> +        662: __ASM_CLAC;                                               \
> +        .popsection;                                                   \
> +        .pushsection .altinstructions, "a";                            \
> +        altinstruction_entry 661b, 662b, X86_FEATURE_SMAP, 3, 3;       \
> +        .popsection

these 661s and 662s alias magic numbers in the alternatives core code,
which could lead to subtle issues.  Surely there is a better way than
having to choose magic numbers which don't collide with anything else in
the source.

~Andrew

> +
> +#define ASM_STAC                                                       \
> +        661: ASM_NOP3;                                                 \
> +        .pushsection .altinstr_replacement, "ax";                      \
> +        662: __ASM_STAC;                                               \
> +        .popsection;                                                   \
> +        .pushsection .altinstructions, "a";                            \
> +        altinstruction_entry 661b, 662b, X86_FEATURE_SMAP, 3, 3;       \
> +        .popsection
>  #else
>  static inline void clac(void)
>  {
> -    if ( boot_cpu_has(X86_FEATURE_SMAP) )
> -        asm volatile (__stringify(__ASM_CLAC) : : : "memory");
> +    /* Note: a barrier is implicit in alternative() */
> +    alternative(ASM_NOP3, __stringify(__ASM_CLAC), X86_FEATURE_SMAP);
>  }
>  
>  static inline void stac(void)
>  {
> -    if ( boot_cpu_has(X86_FEATURE_SMAP) )
> -        asm volatile (__stringify(__ASM_STAC) : : : "memory");
> +    /* Note: a barrier is implicit in alternative() */
> +    alternative(ASM_NOP3, __stringify(__ASM_STAC), X86_FEATURE_SMAP);
>  }
>  #endif
>  

  reply	other threads:[~2014-05-26 15:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  7:27 [PATCH 0/3] x86: Use alternative mechanism to define CLAC/STAC Feng Wu
2014-05-26  7:27 ` [PATCH 1/3] x86: Add definitions for NOP operation Feng Wu
2014-05-26 15:04   ` Andrew Cooper
2014-05-26  7:27 ` [PATCH 2/3] x86: Port the basic alternative mechanism from Linux to Xen Feng Wu
2014-05-26 15:40   ` Andrew Cooper
2014-05-26 16:16     ` Jan Beulich
2014-05-27  6:13     ` Wu, Feng
2014-05-27  9:30       ` Jan Beulich
2014-05-27 15:35   ` Jan Beulich
2014-05-26  7:27 ` [PATCH 3/3] x86: Use alternative mechanism to define CLAC/STAC Feng Wu
2014-05-26 15:49   ` Andrew Cooper [this message]
2014-05-26 16:18     ` Jan Beulich
2014-05-26 16:22       ` Andrew Cooper
2014-05-27  6:24     ` Wu, Feng
2014-05-27 15:42   ` Jan Beulich

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=5383628D.4000907@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=feng.wu@intel.com \
    --cc=keir.xen@gmail.com \
    --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).