From: Alan Cox <alan@redhat.com>
To: hpa@zytor.com (H. Peter Anvin)
Cc: jgarzik@pobox.com (Jeff Garzik),
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 17:49:45 -0500 (EST) [thread overview]
Message-ID: <200303132249.h2DMnj912399@devserv.devel.redhat.com> (raw)
In-Reply-To: <3E70E4B8.2010600@zytor.com> from "H. Peter Anvin" at Mar 13, 2003 12:06:16 PM
> > 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.
I have to admit I'd be more comfortable if we only set those bits IFF
we know they are valid to check, not so much because we need to right now
but out of a desire to make less mistakes possible
next prev parent reply other threads:[~2003-03-13 22:39 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
2003-03-13 22:49 ` Alan Cox [this message]
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=200303132249.h2DMnj912399@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=davej@suse.de \
--cc=hpa@zytor.com \
--cc=jgarzik@pobox.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