From: "Jan Beulich" <jbeulich@novell.com>
To: "Michael Buesch" <mb@bu3sch.de>
Cc: <jgarzik@pobox.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix Intel RNG detection
Date: Thu, 27 Jul 2006 16:16:21 +0100 [thread overview]
Message-ID: <44C8F4E5.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200607271623.48023.mb@bu3sch.de>
>> +#ifdef CONFIG_SMP
>> +static volatile char __initdata waitflag;
>
>I don't think we want to add yet another use of volatile
>(see the kernel archives for why).
>Use memory barriers instead, please.
I can certainly do that.
>> +#define waitflag err
>
>That's really confusing magic.
Any better idea? I just wanted to prevent adding another #ifdef CONFIG_SMP, and since it doesn't matter where the write
goes for UP, doing it that way seemed the simplest solution.
>> + writeb(0xff, mem);
>> + writeb(0x90, mem);
>> + mfg = readb(mem + 0);
>> + dvc = readb(mem + 1);
>> + writeb(0xff, mem);
>
>Do these magic registers have names? Possible to use #defines for it?
While one could certainly make up names for them (the documentation of the functionality used here isn't the best I've
seen), I generally dislike creating defines when their values are used just in a single place *and* when their naming
can at best be artificial (i.e. doesn't serve documentation purposes). But if you and/or Jeff insist, I can certainly do
a change like that.
Jan
Jan
next prev parent reply other threads:[~2006-07-27 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 11:23 [PATCH] fix Intel RNG detection Jan Beulich
2006-07-27 14:23 ` Michael Buesch
2006-07-27 15:16 ` Jan Beulich [this message]
2006-07-27 15:18 ` gmu 2k6
2006-07-27 15:35 ` gmu 2k6
2006-07-27 15:43 ` Jan Beulich
2006-07-27 15:51 ` gmu 2k6
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=44C8F4E5.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.