From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: Fix build following c/s 623c720f "x86: use CLFLUSHOPT when available"
Date: Fri, 12 Feb 2016 09:51:10 +0000 [thread overview]
Message-ID: <56BDAB0E.3050208@citrix.com> (raw)
In-Reply-To: <56BDA49A02000078000D146C@prv-mh.provo.novell.com>
On 12/02/16 08:23, Jan Beulich wrote:
>>>> On 11.02.16 at 20:25, <andrew.cooper3@citrix.com> 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.
> What gas version is this? I just checked with 2.20, which has no
> problem combining an explicit with a generated REX prefix.
bash-4.2$ as --version
GNU assembler version 2.23.52.0.1-30.el7_1.2 20130226
> Or
> wait, no, your description of the issue is wrong: It actually is the
> folding of the two REX prefixes which causes the problem,
This is what I said. What do you think I meant with "trouble combining
the" ?
> since
> that results in the replacement instruction being one byte longer
> than the to be replaced one.
But that is still the case with an explicit %ds override. The assembler
still has to insert an extra byte somehow.
>
>> 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>
> I think before committing I'll extend your patch by introducing
> and using Linux'es NOP_DS_PREFIX.
Ok.
~Andrew
next prev parent reply other threads:[~2016-02-12 9:51 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
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 [this message]
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=56BDAB0E.3050208@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.