linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	linux-arch@vger.kernel.org, mingo@kernel.org,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	linux-s390@vger.kernel.org, bp@suse.de, linux@roeck-us.net,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	rostedt@goodmis.org
Subject: Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit
Date: Mon, 5 Oct 2015 19:09:14 +0200	[thread overview]
Message-ID: <20151005170914.GM14464@wotan.suse.de> (raw)
In-Reply-To: <8902671.32Mbh7QhE4@wuerfel>

On Sun, Oct 04, 2015 at 09:02:04PM +0200, Arnd Bergmann wrote:
> On Saturday 03 October 2015 01:53:46 Luis R. Rodriguez wrote:
> > > 
> > > Hmm, my gut feeling tells me that your approach won't solve the problem
> > > in general. s390 PCI is just weird in many ways and it will occasionally
> > > suffer from problems like this (as do other aspects of the s390 architecture
> > > that are unlike the rest of the world).
> > > 
> > > Maybe Martin and Heiko can comment on this, they may have a preference
> > > from the s390 point of view.
> > 
> > Hrm, so S390 is quirky is really odd ways that no other architecture is or
> > is at least for now not expected to be ?
> 
> Absolutely correct. It is the only architecture I'm aware of that tries to
> support PCI that does not use pointer dereferences for MMIO.

So its not worth it to have a formal semantic via Kconfig for this and are
happy with the status quo of having to find out through a bot compile test
any changes in this domain fails?

  Luis

  reply	other threads:[~2015-10-05 17:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29  0:17 [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit Luis R. Rodriguez
2015-08-29  2:13 ` Randy Dunlap
2015-10-02 23:17   ` Luis R. Rodriguez
2015-10-04  0:14     ` Randy Dunlap
2015-10-05 16:58       ` Luis R. Rodriguez
2015-08-29 15:25 ` Christoph Hellwig
2015-09-03  1:45   ` Luis R. Rodriguez
2015-08-30 19:30 ` Arnd Bergmann
2015-09-03  1:44   ` Luis R. Rodriguez
2015-09-03  1:47     ` Luis R. Rodriguez
2015-09-08  9:54       ` Luis R. Rodriguez
2015-09-08 13:42     ` Arnd Bergmann
2015-09-11  8:14       ` Martin Schwidefsky
2015-10-03  0:04         ` Luis R. Rodriguez
2015-10-02 23:53       ` Luis R. Rodriguez
2015-10-04 19:02         ` Arnd Bergmann
2015-10-05 17:09           ` Luis R. Rodriguez [this message]
2015-10-06 11:15             ` Martin Schwidefsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151005170914.GM14464@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@suse.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mcgrof@do-not-panic.com \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=schwidefsky@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).