Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1218002

Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit

From "Luis R. Rodriguez" <mcgrof@suse.com>
Newsgroups linux.kernel
Subject Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit
Date 2015-09-03 03:50 +0200
Message-ID <q4rP3-5Ru-7@gated-at.bofh.it> (permalink)
References <q2C2d-2c4-3@gated-at.bofh.it> <q2QeS-5LL-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Sat, Aug 29, 2015 at 08:25:05AM -0700, Christoph Hellwig wrote:
> On Fri, Aug 28, 2015 at 05:17:27PM -0700, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@suse.com>
> > 
> > The S390 architecture requires a custom pci_iomap() implementation
> > as the asm-generic implementation assumes there are disjunctions
> > between PCI BARs, and on S390 PCI BAR are not disjunctive, S390 requires
> > the bar parameter in order to find the corresponding device and create
> > the mapping cookie.
> > 
> > This clash with the asm-generic pci_iomap() implementation is implicit,
> > there are no current semantics to make this incompatability explicit.
> > Make the S390 PCI BAR non-disjunction incompatibility explicit, and
> > also pave the way for alternative incompatibilities to be defined.
> > 
> > While at it, as with the ioremap*() variants, since we have no clear
> > semantics yet well defined provide a solution for them that returns
> > NULL. This allows architectures to move forward by defining pci_ioremap*()
> > variants without requiring immediate changes to all architectures. Each
> > architecture then can implement their own solution as needed and
> > when they get to it.
> 
> Now that you have the config symbol available why not move the S390
> implementation to generic code based on that can kill of
> asm/pci_iomap.h?  Seems like we're really not dealing with something
> inherent to the architecture, but two possible implementations based
> on architecture constraints.

That would be the other approach to take too, but perhaps that can wait
until yet another architecture with similar requirement pops up.

 Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit "Luis R. Rodriguez" <mcgrof@do-not-panic.com> - 2015-08-29 02:20 +0200
  Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements  explicit Randy Dunlap <rdunlap@infradead.org> - 2015-08-29 04:20 +0200
  Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements  explicit Christoph Hellwig <hch@infradead.org> - 2015-08-29 17:30 +0200
    Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements  explicit "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-03 03:50 +0200
  Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit Arnd Bergmann <arnd@arndb.de> - 2015-08-30 21:40 +0200
    Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements  explicit "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-03 03:50 +0200
      Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit "Luis R. Rodriguez" <mcgrof@do-not-panic.com> - 2015-09-03 03:50 +0200

csiph-web