From: Laszlo Ersek <lersek@redhat.com>
To: "Ni, Ruiyu" <ruiyu.ni@Intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Michael Kinney <michael.d.kinney@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH] MdePkg/BaseSynchronizationLib: fix XADD operands in GCC IA32/X64 assembly
Date: Wed, 26 Sep 2018 14:04:36 +0200 [thread overview]
Message-ID: <9175ba14-99aa-6ed2-24ca-26af69dd5bf5@redhat.com> (raw)
In-Reply-To: <c6d158e1-fa21-3cd8-c548-1006edf637aa@Intel.com>
On 09/26/18 11:34, Ni, Ruiyu wrote:
> On 9/26/2018 5:05 PM, Laszlo Ersek wrote:
>> Hi,
>>
>> On 09/25/18 21:48, Laszlo Ersek wrote:
>>> Currently, "gcc-4.8.5-28.el7_5.1.x86_64" generates the following code
>>> for
>>> me, from the XADD inline assembly added to "X64/GccInline.c" in commit
>>> 17634d026f96:
>>>
>>>> 0000000000004383 <InternalSyncIncrement>:
>>>> UINT32
>>>> EFIAPI
>>>> InternalSyncIncrement (
>>>> IN volatile UINT32 *Value
>>>> )
>>>> {
>>>> 4383: 55 push %rbp
>>>> 4384: 48 89 e5 mov %rsp,%rbp
>>>> 4387: 48 83 ec 10 sub $0x10,%rsp
>>>> 438b: 48 89 4d 10 mov %rcx,0x10(%rbp)
>>>> UINT32 Result;
>>>>
>>>> __asm__ __volatile__ (
>>>> 438f: 48 8b 55 10 mov 0x10(%rbp),%rdx
>>>> 4393: 48 8b 45 10 mov 0x10(%rbp),%rax
>>>> 4397: b8 01 00 00 00 mov $0x1,%eax
>>>> 439c: f0 0f c1 00 lock xadd %eax,(%rax)
>>>> 43a0: ff c0 inc %eax
>>>> 43a2: 89 45 fc mov %eax,-0x4(%rbp)
>>>> : "m" (*Value) // %2
>>>> : "memory",
>>>> "cc"
>>>> );
>>>>
>>>> return Result;
>>>> 43a5: 8b 45 fc mov -0x4(%rbp),%eax
>>>> }
>>>> 43a8: c9 leaveq
>>>> 43a9: c3 retq
>>>>
>>>
>>> The MOV $0X1,%EAX instruction corrupts the address of Value in %RAX
>>> before
>>> we reach the XADD instruction. In fact, it makes no sense for XADD to
>>> use
>>> %EAX as source operand and (%RAX) as destination operand at the same
>>> time.
>>
>> may I get a fast review for this patch, please? The regression from
>> commit 17634d026f96 prevents OVMF from booting.
>
> Sure. Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
Thanks, Ray! Commit 8a94eb9283fa.
Laszlo
next prev parent reply other threads:[~2018-09-26 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:48 [PATCH] MdePkg/BaseSynchronizationLib: fix XADD operands in GCC IA32/X64 assembly Laszlo Ersek
2018-09-26 9:05 ` Laszlo Ersek
2018-09-26 9:34 ` Ni, Ruiyu
2018-09-26 12:04 ` Laszlo Ersek [this message]
[not found] ` <8ecbcc60-8e0f-e418-614e-666aa7fb007b@Intel.com>
2018-09-27 9:46 ` Shao, Ming
[not found] ` <0D32B2537B667F42AD320D616D521AF738B92170@shsmsx102.ccr.corp.intel.com>
2018-09-27 10:19 ` Laszlo Ersek
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-list 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=9175ba14-99aa-6ed2-24ca-26af69dd5bf5@redhat.com \
--to=devel@edk2.groups.io \
/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