From: Paul Menage <menage@google.com>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] ACPI global lock macros
Date: Thu, 11 Dec 2003 00:20:14 -0800 [thread overview]
Message-ID: <3FD828BE.7020906@google.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720C21@PDSMSX403.ccr.corp.intel.com>
Yu, Luming wrote:
>
>
> 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 !
Oops - the version I posted differed in one character from the version
that I'd compiled - I'd just used "sbb" in the working version and let
the compiler figure out which version to use.
>
> 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"); \
Yes, that would work too, but I don't like forcing the asm to use
particular registers when there's no good reason to do so.
>
>
> PS. I'm very curious about how could you find this bug.
It was mainly down to the differences between the i386 and x86_64
versions, and trying to understand the reasons for those differences,
and indeed how the entire set of macros worked at all.
Paul
next prev parent reply other threads:[~2003-12-11 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 7:06 [ACPI] ACPI global lock macros Yu, Luming
2003-12-11 8:07 ` Andi Kleen
2003-12-11 8:27 ` Paul Menage
2003-12-11 8:20 ` Paul Menage [this message]
-- 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=3FD828BE.7020906@google.com \
--to=menage@google.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.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