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
| ||
|
Date: Sun, 13 Jan 2008 09:03:11 -0800 From: Arjan van de Ven <arjan@...radead.org> To: tcamuso@...hat.com Cc: Ivan Kokshaysky <ink@...assic.park.msu.ru>, Greg KH <greg@...ah.com>, Matthew Wilcox <matthew@....cx>, Linus Torvalds <torvalds@...ux-foundation.org>, Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>, linux-pci@...ey.karlin.mff.cuni.cz, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Martin Mares <mj@....cz>, Loic Prylli <loic@...i.com>, Prarit Bhargava <prarit@...hat.com>, "Chumbalkar, Nagananda" <Nagananda.Chumbalkar@...com>, "Schoeller, Patrick (Linux - Houston, TX)" <Patrick.Schoeller@...com>, Bhavana Nagendra <bnagendr@...hat.com> Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in On Sun, 13 Jan 2008 07:43:11 -0500 Tony Camuso <tcamuso@...hat.com> wrote: > Arjan van de Ven wrote: > > On Sat, 12 Jan 2008 20:36:59 -0500 > > Tony Camuso <tcamuso@...hat.com> wrote: > > > > > > Just about NOBODY has devices that need the extended config space. > > At all. > > The PCI express spec requires the platform to provide access to this > space for express-compliance. PLATFORM not OS :) Windows isn't using it in the server space, and only in the client space it recently started considering it. > More devices will be using this space > as express becomes the dominant IO bus technology. sure in like 2009 maybe. > Which is why Loic's proposal and Ivan's implementation of it is so > elegant. It solves all these problems in one sweep, and eliminates > the code rendered cruft by Ivan's patch. A two-fer, by my reckoning. > > >> In other words, for x86, I don't think we need to worry about Port > >> IO config access ever going away at all. > > > > You're wrong there. Sad to say, but you're wrong there. > > > > The PCI spec provides for conf1 as an architected solution. It's not > going away, and especially not in x86 land where Port IO is built-in > to the CPU. again sadly you're wrong. -- If you want to reach me at my work email, use arjan@...ux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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