From: Jeff Garzik <jgarzik@pobox.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, davej@suse.de, alan@redhat.com,
torvalds@transmeta.com
Subject: Re: [PATCH] cpu/hw_random cleanups
Date: Thu, 13 Mar 2003 15:09:34 -0500 [thread overview]
Message-ID: <20030313200934.GA17643@gtf.org> (raw)
In-Reply-To: <3E70E4B8.2010600@zytor.com>
On Thu, Mar 13, 2003 at 12:06:16PM -0800, H. Peter Anvin wrote:
> Jeff Garzik wrote:
> >For x86 experts, the new cpu cap words are what needs looking over.
> >For example, I wonder if storing Intel's cpuid(0x00000001) ecx
> >register output is wise on older Intel cpus. I worry about garbage
> >appearing there. Is that a false worry?
> >
>
> Yes; it should be completely safe.
noted
> >===== arch/i386/kernel/cpu/centaur.c 1.7 vs edited =====
> >--- 1.7/arch/i386/kernel/cpu/centaur.c Tue Mar 11 21:35:40 2003
> >+++ edited/arch/i386/kernel/cpu/centaur.c Thu Mar 13 13:31:08 2003
> >@@ -256,9 +256,10 @@
> > if (cpuid_eax(0xC0000000) >= 0xC0000001) {
> > set_bit(X86_FEATURE_CENTAUR_EFF, c->x86_capability);
> >
>
> There is also no need to set a special feature bit for the existence of
> the feature flags. If they are not present the additional capability
> word will simply be zero.
Thanks, fixed.
Jeff
next prev parent reply other threads:[~2003-03-13 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 18:43 [PATCH] cpu/hw_random cleanups Jeff Garzik
2003-03-13 20:06 ` H. Peter Anvin
2003-03-13 20:09 ` Jeff Garzik [this message]
2003-03-13 22:49 ` Alan Cox
2003-03-13 22:52 ` H. Peter Anvin
2003-03-13 21:39 ` Robert Love
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=20030313200934.GA17643@gtf.org \
--to=jgarzik@pobox.com \
--cc=alan@redhat.com \
--cc=davej@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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