[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3669a28a055344a792b51439c953fd30@AcuMS.aculab.com>
Date: Fri, 6 May 2022 13:28:42 +0000
From: David Laight <David.Laight@...LAB.COM>
To: "'Maciej W. Rozycki'" <macro@...am.me.uk>
CC: Arnd Bergmann <arnd@...nel.org>, Rich Felker <dalias@...c.org>,
"open list:IA64 (Itanium) PLATFORM" <linux-ia64@...r.kernel.org>,
"open list:SUPERH" <linux-sh@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"open list:MIPS" <linux-mips@...r.kernel.org>,
"James E.J. Bottomley" <James.Bottomley@...senpartnership.com>,
"open list:SPARC + UltraSPARC (sparc/sparc64)"
<sparclinux@...r.kernel.org>,
"open list:RISC-V ARCHITECTURE" <linux-riscv@...ts.infradead.org>,
Will Deacon <will@...nel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Helge Deller <deller@....de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
Russell King <linux@...linux.org.uk>,
Ingo Molnar <mingo@...hat.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-pci <linux-pci@...r.kernel.org>,
Bjorn Helgaas <helgaas@...nel.org>,
Matt Turner <mattst88@...il.com>,
Albert Ou <aou@...s.berkeley.edu>,
Arnd Bergmann <arnd@...db.de>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
"open list:M68K ARCHITECTURE" <linux-m68k@...ts.linux-m68k.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Paul Walmsley <paul.walmsley@...ive.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
"moderated list:ARM PORT" <linux-arm-kernel@...ts.infradead.org>,
Richard Henderson <rth@...ddle.net>,
Michal Simek <monstr@...str.eu>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
"open list:PARISC ARCHITECTURE" <linux-parisc@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Palmer Dabbelt <palmer@...belt.com>,
"open list:ALPHA PORT" <linux-alpha@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@...ts.ozlabs.org>,
"David S. Miller" <davem@...emloft.net>
Subject: RE: [RFC v2 01/39] Kconfig: introduce HAS_IOPORT option and select it
as necessary
From: Maciej W. Rozycki
> Sent: 06 May 2022 14:15
> On Fri, 6 May 2022, David Laight wrote:
>
> > > The PCI configuration space was retrofitted into x86 systems (and is
> > > accessed in an awkward manner with them), but with a new design such a
> > > clean approach is most welcome IMHO. Thank you for your explanation.
> >
> > Actually I think x86 was the initial system for PCI.
> > The PCI config space 'mess' is all about trying to make
> > something that wouldn't break existing memory maps.
>
> It was retrofitted in that x86 systems already existed for ~15 years when
> PCI came into picture. Therefore the makers of the CPU ISA couldn't have
> envisaged the need for config access instructions like they did for memory
> and port access.
Rev 2.0 of the PCI spec (1993) defines two mechanisms for config cycles.
#2 is probably the first one and maps all of PCI config space into
4k of IO space (PCI bridges aren't supported).
#1 requires a pair of accesses (and SMP locking).
Neither is really horrid.
For horrid try the ISApnp interface.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists