From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86: Fix build following c/s 623c720f "x86: use CLFLUSHOPT when available"
Date: Thu, 11 Feb 2016 19:41:23 +0000 [thread overview]
Message-ID: <56BCE3E3.8050105@citrix.com> (raw)
In-Reply-To: <1455218743-12751-1-git-send-email-andrew.cooper3@citrix.com>
On 11/02/16 19:25, Andrew Cooper wrote:
> CentOS 7 gets into trouble when compiling Xen citing:
>
> flushtlb.c: Assembler messages:
> flushtlb.c:149: Error: value of 256 too large for field of 1 bytes at 1
>
> The line number is wrong, and the error message not helpful. It turns out
> that the intermediate generated assembly was
>
> # 139 "arch/x86/flushtlb.c" 1
> 661:
> rex clflush (%r15)
> 662:
> .pushsection .altinstructions,"a"
>
> and it was having trouble combining the explicit REX prefix with the REX.B
> required for the use of %r15.
>
> Follow what Linux does and use a redundant %ds prefix instead, for a final
> generated instruction of `3e 41 0f ae 3f`
>
> While modifying this line, fix the indentation which was out by one space.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> ---
> xen/arch/x86/flushtlb.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/xen/arch/x86/flushtlb.c b/xen/arch/x86/flushtlb.c
> index 90a004f..727434e 100644
> --- a/xen/arch/x86/flushtlb.c
> +++ b/xen/arch/x86/flushtlb.c
> @@ -141,10 +141,10 @@ void flush_area_local(const void *va, unsigned int flags)
> {
> alternative(ASM_NOP3, "sfence", X86_FEATURE_CLFLUSHOPT);
> for ( i = 0; i < sz; i += c->x86_clflush_size )
> - alternative_input("rex clflush %0",
> - "data16 clflush %0",
> - X86_FEATURE_CLFLUSHOPT,
> - "m" (((const char *)va)[i]));
> + alternative_input(".byte 0x3e; clflush %0", /* %ds override. */
> + "data16 clflush %0", /* clflushopt. */
> + X86_FEATURE_CLFLUSHOPT,
> + "m" (((const char *)va)[i]));
> }
> else
> {
It turns out that Clang is far more useful at diagnosing this issue than
GCC.
flushtlb.c:144:18: error: invalid instruction mnemonic 'rex'
alternative_input("rex clflush %0",
^
/local/xen.git/xen/include/asm/alternative.h:98:16: note: expanded from
macro 'alternative_input'
asm volatile (ALTERNATIVE(oldinstr, newinstr, feature) \
^
/local/xen.git/xen/include/asm/alternative.h:60:2: note: expanded from
macro 'ALTERNATIVE'
OLDINSTR(oldinstr) \
^
/local/xen.git/xen/include/asm/alternative.h:28:40: note: expanded from
macro 'OLDINSTR'
#define OLDINSTR(oldinstr) "661:\n\t" oldinstr "\n662:\n"
^
<inline asm>:2:2: note: instantiated into assembly here
rex clflush (%r15,%rdx)
^~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
~Andrew
next prev parent reply other threads:[~2016-02-11 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 19:25 [PATCH] x86: Fix build following c/s 623c720f "x86: use CLFLUSHOPT when available" Andrew Cooper
2016-02-11 19:41 ` Andrew Cooper [this message]
2016-02-12 8:13 ` Jan Beulich
2016-02-12 9:47 ` Andrew Cooper
2016-02-11 22:14 ` Doug Goldstein
2016-02-12 8:23 ` Jan Beulich
2016-02-12 9:51 ` Andrew Cooper
2016-02-12 10:00 ` Jan Beulich
2016-02-12 10:02 ` Andrew Cooper
2016-02-12 10:12 ` Jan Beulich
2016-02-12 10:50 ` Andrew Cooper
2016-02-12 10:57 ` Jan Beulich
2016-02-12 11:05 ` 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=56BCE3E3.8050105@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.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 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.