linux-kernel - Re: [patch] pci: revert "PCI: remove transparent bridge sizing"

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:	Thu, 27 Mar 2008 09:27:28 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Gary Hade <garyhade@...ibm.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Meyer <thomas@...3r.de>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Natalie Protasevich <protasnb@...il.com>, pm@...ian.org
Subject: Re: [patch] pci: revert "PCI: remove transparent bridge sizing"


On Wed, 2008-03-26 at 22:07 +0000, Alan Cox wrote:
> > PCI bridges at zero is perfectly valid indeed and I'm sure we have that
> > around at least for IO space. In fact, I'm surprised you don't have that
> > on x86. Typically, things like an HT segment with a P2P bridge and
> > behind that bridge an ISA bridge could well have the P2P bridge with a
> > resource forwarding 0...0x1000 IO downstream for example even on x86
> > no ? (I'm not -that- familiar with the crazyness of legacy ISA on x86
> > but I've definitely seen such setup on other archs).
> 
> On a PC system 0x00-0xFF are motherboard resources (sometimes chipset,
> some even swallowed by the CPU in certain cases) so 0 as disabled is sort
> of safe but as shown by the pci_enable_device_bars replacement code - not
> a good idea neccessarily.
> 
> A lot of driver code does assume 0 == unavailable/off/disabled including
> large chunks of serial, ata, ide and probably other subsystems.

True, and we do try to avoid allocating resources at 0 most of the time,
but it happens, and in the case of bridges, it can make somewhat sense
(more in fact than for devices I'd say).

Cheers,
Ben.


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