public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org, davej@suse.de,
	torvalds@transmeta.com
Subject: Re: [PATCH] cpu/hw_random cleanups
Date: Thu, 13 Mar 2003 14:52:32 -0800	[thread overview]
Message-ID: <3E710BB0.8000300@zytor.com> (raw)
In-Reply-To: <200303132249.h2DMnj912399@devserv.devel.redhat.com>

Alan Cox wrote:
>>>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
>

The problem is that you risk exactly the opposite mistake -- it's called
"anticompetitive feature lockout."  Intel would happily tell you to do
it; in fact, if you follow Intel guidelines or use their sample code it
will treat anything that isn't an Intel chip like a 486.

If any chip that claims to support CPUID level 00000001h reports
anything other than zero in this field, that chip is broken and we
should deal with it as a chip-specific bug.  At this point there are no
chips which are known to have this bug (and there are, after all, only a
finite number of chips out there.)

	-hpa


  reply	other threads:[~2003-03-13 22:42 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
2003-03-13 22:52     ` H. Peter Anvin [this message]
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=3E710BB0.8000300@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@redhat.com \
    --cc=davej@suse.de \
    --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