linux-kernel - Re: [patch 0/9] x86, xsave: xsave/xrstor support

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: <20080801144917.GY23938@one.firstfloor.org>
Date:	Fri, 1 Aug 2008 16:49:17 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Rene Herman <rene.herman@...access.nl>
Cc:	Ingo Molnar <mingo@...e.hu>, Wolfram Sang <w.sang@...gutronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Wim Van Sebroeck <wim@...ana.be>,
	Pádraig Brady <P@...igBrady.com>,
	Andi Kleen <andi@...stfloor.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"roland@...hat.com" <roland@...hat.com>,
	"drepper@...hat.com" <drepper@...hat.com>,
	"mikpe@...uu.se" <mikpe@...uu.se>,
	"chrisw@...s-sol.org" <chrisw@...s-sol.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/9] x86, xsave: xsave/xrstor support

On Fri, Aug 01, 2008 at 04:27:53PM +0200, Rene Herman wrote:
> On 01-08-08 11:51, Ingo Molnar wrote:
> 
> >find attached below a newer version of the original list i published 
> >half a year ago:
> >
> >   http://people.redhat.com/mingo/auto-qa-patches/Kconfig-qa.patch
> >
> >these are just pragmatic local hacks to get things going. (There are 
> >more per machine quirks as well.)
> >
> >i have not used a BROKEN annotation because CONFIG_BROKEN is 
> >impractical: it just kills code altogether, indiscriminately. There's no 
> >way for users to enable CONFIG_BROKEN in the upstream kernel - nothing 
> >selects it and it's not an interactive option either.
> >
> >So by all means if we mark a driver or a kernel feature as 
> >CONFIG_BROKEN, it's killed altogether for all practical purposes.
> >
> >What we'd need is some more gradual approach: for example a way to mark 
> >"drivers that are not expected to boot on a whitebox PC", without 
> >removing them altogether via a CONFIG_BROKEN dependency - often it's 
> >hardware that cannot be probed safely.
> 
> For real ISA at the least, the best fix I feel is just not go grabbing 
> resources without anything (ie, ISAPnP) or anyone (ie, the user) telling 

Really old systems don't have isapnp. Neither have smbus devices.

> us that's where the hardware's at.

That would mean the users on these systems would need to add tons
of obscure command line options.

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