From: Mikael Pettersson <mikpe@it.uu.se>
To: juergen127@kreuzholzen.de, linux-kernel@vger.kernel.org
Subject: Re: Geode-GX1 processor in 2.6.21
Date: Mon, 30 Apr 2007 14:13:52 +0200 (MEST) [thread overview]
Message-ID: <200704301213.l3UCDqgN018906@harpo.it.uu.se> (raw)
On Mon, 30 Apr 2007 12:51:05 +0200, Juergen Beisert wrote:
> setCx86(CX86_CCR2, getCx86(CX86_CCR2) | 0x88);
>
> If this register is 0x00 before, it is still 0x00 after this line. If I change
> the line into this:
>
> ccr2 = getCx86(CX86_CCR2);
> ccr2 |= 0x88;
> setCx86(CX86_CCR2, ccr2);
>
> register ccr2 is 0x88 after the setCx86 call and the power saving feature is
> active (and BTW: the TSC is useless then, because it also stops when the CPU
> runs into a HLT instruction).
>
> setCx86 and getCx86 are macros defined in include/asm-i386/processor.h:
>
> #define getCx86(reg) ({ outb((reg), 0x22); inb(0x23); })
>
> #define setCx86(reg, data) do { \
> outb((reg), 0x22); \
> outb((data), 0x23); \
> } while (0)
>
> Maybe the compiler does the wrong thing if someone uses these macros in the
> same instruction?
The compiler is fine, it's the setCx86() macro that is utter crap
because it fails to behave like a function by not evaluating its
arguments before performing its outb() statements.
Converting them to static inlines would be the best solution. Something like
static inline u8 getCx86(unsigned int reg)
{
outb(reg, 0x22);
return inb(0x23);
}
static inline void setCx86(unsigned int reg, u8 data)
{
outb(reg, 0x22);
outb(data, 0x23);
}
ought to work.
/Mikael
next reply other threads:[~2007-04-30 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 12:13 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-30 10:51 Juergen Beisert
2007-04-30 12:20 ` Andreas Mohr
2007-04-30 13:16 ` Juergen Beisert
2007-04-30 15:02 ` Alan Cox
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=200704301213.l3UCDqgN018906@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=juergen127@kreuzholzen.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®