From: "Yu, Luming" <luming.yu@intel.com>
To: "Paul Menage" <menage@google.com>, <agrover@groveronline.com>
Cc: <linux-kernel@vger.kernel.org>, <acpi-devel@lists.sourceforge.net>
Subject: RE: [ACPI] ACPI global lock macros
Date: Thu, 11 Dec 2003 15:06:10 +0800 [thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F8401720C21@PDSMSX403.ccr.corp.intel.com> (raw)
>>#define ACPI_ACQUIRE_GLOBAL_LOCK(GLptr, Acq) \
>> do { \
>> asm volatile("1:movl (%1),%%eax;" \
>> "movl %%eax,%%edx;" \
>> "andl %2,%%edx;" \
>> "btsl $0x1,%%edx;" \
>> "adcl $0x0,%%edx;" \
>> "lock; cmpxchgl %%edx,(%1);" \
>> "jnz 1b;" \
>> "cmpb $0x3,%%dl;" \
>> "sbbl %0,%0" \
>> :"=r"(Acq):"r"(GLptr),"i"(~1L):"dx", "ax"); \
>> } while(0)
Above code have a bug! Considering below code:
u8 acquired = FALSE;
ACPI_ACQUIRE_GLOBAL_LOC(acpi_gbl_common_fACS.global_lock, acquired);
if(acquired) {
....
}
Gcc will complain " ERROR: '%cl' not allowed with sbbl ". And I think any other compiler will
complain that too !
How about below changes to your proposal code.
< "sbbl %0,%0" \
< :"=r"(Acq):"r"(GLptr),"i"(~1L):"dx","ax"); \
---
> "sbbl %%eax,%%eax" \
> :"=a"(Acq):"r"(GLptr),"i"(~1L):"dx"); \
PS. I'm very curious about how could you find this bug.
Thanks
Luming
next reply other threads:[~2003-12-11 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 7:06 Yu, Luming [this message]
2003-12-11 8:07 ` [ACPI] ACPI global lock macros Andi Kleen
2003-12-11 8:27 ` Paul Menage
2003-12-11 8:20 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2003-12-11 7:27 Yu, Luming
2003-12-11 17:46 ` Nate Lawson
2003-12-09 18:20 Grover, Andrew
2003-12-09 19:04 ` Paul Menage
2003-12-09 19:03 ` David Mosberger
2003-12-09 9:22 Paul Menage
2003-12-10 7:45 ` [ACPI] " Andi Kleen
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=3ACA40606221794F80A5670F0AF15F8401720C21@PDSMSX403.ccr.corp.intel.com \
--to=luming.yu@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=agrover@groveronline.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
/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).