Re: Inconsistent CPUID result
From: babel2017 (babel2017_at_aol.com)
Date: 02/16/04
- Next message: SPH: "Re: GNU as vs nasm?"
- Previous message: RoWsRaIrTiEo : "Re: input & output in assembly"
- In reply to: Matt Taylor: "Re: Inconsistent CPUID result"
- Next in thread: Matt Taylor: "Re: Inconsistent CPUID result"
- Reply: Matt Taylor: "Re: Inconsistent CPUID result"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 16 Feb 2004 18:32:27 +0000 (UTC)
"Matt Taylor" <para@tampabay.rr.com> wrote in message news:<gsQXb.173836$fH2.98723@twister.tampabay.rr.com>...
> "Michael Brown" <see@signature.below> wrote in message
> news:MuIXb.45035$9k7.921170@news.xtra.co.nz...
> > babel2017 wrote:
> > > Hi
> > >
> > > I use a machine fingerprint for license control. Have just introduced
> > > CPUID into the mix and it's out for testing. One tester's CPU
> > > suddenly decided to change its name! It was "AMD Athlon(tm)
> > > Processor" and now it's "AMD Athlon(tm) XP 3000+"! Any clues as to
> > > why this happened and whether it's possible to get consistent results
> > > from CPUID?
> >
> > The name string is user-configurable. If there is a BIOS update applied,
> > there is a chance that it will call the chip something different. For
> > example if the user's CPU is now officially supported, it'll possibly go
> > from "AMD Athlon xxxMHz" to "AMD AthlonXP yyyy". Also, if the user
> > overclocks their machine, the name will change as well. It's far better to
> > use the processor ID functions of CPUID, rather than the name string
> > function.
>
> I might also add that on a dual-processor machine there is an even worse
> problem. Oddly enough, my BIOS initializes my first CPU's name string to
> "AMD Athlon(tm) MP 1600+" second CPU's name string to "AMD Athlon(tm)
> Processor" I wrote a quick & dirty cpuid program to demonstrate this:
>
> C:\Documents and Settings\Matt\Desktop>cpuid
> AMD Athlon(tm) MP 1600+
>
> C:\Documents and Settings\Matt\Desktop>cpuid
> AMD Athlon(tm) Processor
>
> Even if the BIOS did set both names correctly, the steppings can be
> different. In fact I know of one person who ran an "unequal" dual-CPU
> machine with Celerons. The first was 300-something MHz, and the second was
> 400 MHz. One must be wary of this case as well. Either take only the first
> processor into account or take every processor into account.
>
> -Matt
Thanks for all the excellent advice. I think I'll try to use the
processor signature instead. But I'm an assembler newbie (not
counting 6502 in AppleII days!) and am not sure how to select which
processor CPUID reports on in a dual-processor setup. Would be
grateful for advice on that.
For others who pass this way, here's a good link I found:
http://www.intel.com/design/Xeon/applnots/24161825.pdf
- Next message: SPH: "Re: GNU as vs nasm?"
- Previous message: RoWsRaIrTiEo : "Re: input & output in assembly"
- In reply to: Matt Taylor: "Re: Inconsistent CPUID result"
- Next in thread: Matt Taylor: "Re: Inconsistent CPUID result"
- Reply: Matt Taylor: "Re: Inconsistent CPUID result"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|