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]
Date:	Sun, 5 Jul 2009 21:12:51 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <yinghai@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC -tip] x86,apic -- reduce disable_apic usage

[Cyrill Gorcunov - Sun, Jul 05, 2009 at 08:59:47PM +0400]
| [Maciej W. Rozycki - Sun, Jul 05, 2009 at 05:38:52PM +0100]
| | On Sun, 5 Jul 2009, Cyrill Gorcunov wrote:
| | 
| | > Here is an attempt to bring more consistency for apic
| | > presence check. I hope I covered all the code flows.
| | > Though it's RFC. Please review and test if possible.
| | > 
| | > 	-- Cyrill
| | > ---
| | > Instead of messing with (cpu_has_apic|disable_apic)
| | > to check if we have apic functional, better to distinguish
| | > them by logical kind. cpu_has_apic -- to check if we may
| | > use apic functionality, disable_apic -- to note that
| | > apic was disabled via command line.
| | 
| |  How do you set cpu_has_apic for systems with discrete local APICs?  The 
| | CPUID flag is not set in this case.
| | 
| |   Maciej
| | --
| | 
| 
| Well, indeed, somehow forgot about this case. Thanks Maciej!
| The patch should be dropped.
| 
| 	-- Cyrill

Hmm... But if we have no MP table parsed and no "lapic" option
passed we should leave execution in pure PIC mode. Or I miss
something?

	-- Cyrill
--
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