linux-kernel - RE: [X86] Fix up silly i1586 boot message.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.2.00.0910280914590.28170@obet.zrqbmnf.qr>
Date:	Wed, 28 Oct 2009 09:30:33 +0100 (CET)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Yuhong Bao <yuhongbao_386@...mail.com>
cc:	macro@...ux-mips.org, davej@...hat.com,
	linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de,
	hpa@...or.com
Subject: RE: [X86] Fix up silly i1586 boot message.


On Wednesday 2009-10-28 04:08, Yuhong Bao wrote:
> <Pine.LNX.4.55.0805290102340.29522@...ff.in.clinika.pl>
>
>> Intel started it first with picking up a ridiculous number for the family
>> ID for the P4 line. There is no technical justification for not keeping
>> these numbers consecutive.

Once one knows that there are 4 bits for the family field, 15 is not
such a strange value - it is the last value, one could take it as
"reserved, and look elsewhere".

>[...] Intel has assigned family 7 for the original Itanium processor
>[...] there was a bug in original NT 4 truncating family IDs
>returned by CPUID [...]

That would explain why Intel still shows an oldfashioned family=6 on
many contemporary processors (e.g. core i7). BUT, AMD64 processors
have family=15 "almost throughout", and so seem to have at least some
Intel models. So that tells us that either NT4 works, or nobody uses
NT4 on fam15s.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/