linux-kernel - Re: [rfc] hw resource debugging checks

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: <87d4ouw0u9.fsf@basil.nowhere.org>
Date:	Sun, 13 Apr 2008 11:39:10 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, Yinghai Lu <yinghai.lu@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Anvin" <hpa@...or.com>, Arjan van de Ven <arjan@...radead.org>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [rfc] hw resource debugging checks

Ingo Molnar <mingo@...e.hu> writes:

This whole problem just shows that it was a mistake in the first place
to try to redo the BIOS work in Linux. If BIOS doesn't supply MCFG
Linux trying to create one (or in general having generalized resource
allocation) is just a big mess and will cause endless problems.  The
standard resource code is just not up to the task and it needs very
intimate knowledge of the hardware that the kernel shouldn't have.

Again the real fix I think is to just drop all that code in git-x86
again and finally fix LinuxBIOS to do its job properly and pass a
proper MCFG (or just forget about using mmconfig with LinuxBIOS - it
is not that Type1 suddently doesn't work anymore). Then this code
wouldn't be needed at all

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