linux-kernel - Re: regression fixed by using pci=rom

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] [day] [month] [year] [list]

Message-ID: <20080509185425.GC6255@us.ibm.com>
Date:	Fri, 9 May 2008 11:54:26 -0700
From:	Gary Hade <garyhade@...ibm.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Gary Hade <garyhade@...ibm.com>, Ingo Molnar <mingo@...e.hu>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Dave Airlie <airlied@...il.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: regression fixed by using pci=rom

On Fri, May 09, 2008 at 10:26:47AM -0700, Linus Torvalds wrote:
> 
> 
> On Fri, 9 May 2008, Gary Hade wrote:
> > 
> > Ingo, Would you (or others listening to this discussion) know
> > exactly what Windows does with respect to BIOS unassigned
> > expansion ROMs?
> 
> Nobody really seems to know what windows does for *any* resources. And it 
> probably depends on windows version too, and on detailed chipset issues 
> (ie does Windows do the same thing as Linux wrt transparent bridges that 
> still have bus translation resources set up?).
> 
> So the "try to do what Windows does" is something we strive for in 
> particular cases, but it's not an absolute thing, and probably can never 
> even be that in theory. It's more a guideline, especially when we don't 
> know which particular choice is better and both seem otherwise equally 
> good.
> 
> But "doesn't work" always trumps "that's what windows does". Because even 
> if something works under Windows, sometimes Linux drivers simply then act 
> differently (ie they may use PIO vs MMIO, or in the case of graphics they 
> may need ROMs for re-POST'ing while a windows driver is written by the 
> chipset vendor and DTRT without even looking at the BIOS tables)

Yea, this is probably a good explanation of why Windows does run,
presumably without PCI resource allocation issues, on those same
systems where we have struggling with the expansion ROM resource
allocation failures from Linux.

Thanks.

Gary

-- 
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503  IBM T/L: 775-4503
garyhade@...ibm.com
http://www.ibm.com/linux/ltc

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