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.LFD.1.10.0810221630390.24509@ftp.linux-mips.org>
Date:	Wed, 22 Oct 2008 16:41:05 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Cyrill Gorcunov <gorcunov@...il.com>,
	Glauber Costa <glommer@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH -tip] x86: do_boot_cpu - check if we have ESR register

On Wed, 22 Oct 2008, Ingo Molnar wrote:

> i'm wondering - is the server there really that old, that it has no 
> integrated lapic? I.e. it's an i486 SMP box or so? Or perhaps some 
> other, weird SMP box?

 I've been wondering about that too, though the fix is correct either way.  

 Note that all the discrete APIC boxes we have ever supported were 
Pentium-based, either the original P5 (i.e. 60/66MHz) chips which had no 
APIC on chip at all or P54C ones but with the integrated APIC disabled 
(because the systems were 4-way SMP or suchlike and there was no suitable 
chipset component to provide a compatible I/O APIC).

 All the documentation for i486 SMP boxes I was able to track down 
indicated that even if APIC chips were used with them, the whole setup did 
not support the MP table as defined by the MultiProcessor Specification 
and therefore could not be supported by Linux as it is.  And I have never 
come across a specimen to look into it any further.

  Maciej
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ