linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>, Helge Deller <deller@gmx.de>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH-RFC 07/10] parisc: switch to GENERIC_PCI_IOMAP
Date: Sun, 4 Dec 2011 16:42:37 +0200	[thread overview]
Message-ID: <20111204144236.GA21506@redhat.com> (raw)
In-Reply-To: <1323009144.3003.6.camel@dabdike.int.hansenpartnership.com>

On Sun, Dec 04, 2011 at 08:32:24AM -0600, James Bottomley wrote:
> On Sun, 2011-12-04 at 16:30 +0200, Michael S. Tsirkin wrote:
> > On Sun, Dec 04, 2011 at 08:22:34AM -0600, James Bottomley wrote:
> > > On Sun, 2011-12-04 at 12:48 +0200, Michael S. Tsirkin wrote:
> > > > On Thu, Nov 24, 2011 at 10:19:34PM +0200, Michael S. Tsirkin wrote:
> > > > > parisc copied pci_iomap from generic code, probably to avoid
> > > > > pulling the rest of iomap.c in.  Since that's in
> > > > > a separate file now, we can reuse the common implementation.
> > > > > 
> > > > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > > > 
> > > > Sorry to nag, any ACKs/NACKs on the parisc part?
> > > > I intend to send this to Linus if there are no
> > > > objections. Thanks!
> > > 
> > > Next time, send the patch to linux-arch or linux-parisc ... it helps to
> > > get people to review it. Although this one looks completely trivial,
> > > unless I'm missing something?
> > 
> > I think it's trivial but I don't have the setup to even compile it so
> > depend on someone to ack.
> > 
> > > Obviously there was a bit of a brain fart when this was done: the parisc
> > > piece shouldn't be a copy of the generic code: we don't have native i/o
> > > ports and emulation is pretty expensive, so we should prefer
> > > IORESOURCE_MEM over IORESOURCE_IO when both are available  ... but even
> > > on x86, memory mapping is faster (although not by the order of magnitude
> > > it is on parisc), so it looks like you could fix this in the generic
> > > code.
> > > 
> > > James
> > 
> > AFAIK, on PCI a resource is either IO or MEM, but never both.
> > What am I missing?
> 
> Could be ... I know we've had issues in the past with standard drivers
> like the sym53c8xx which map via both and operate far less efficiently
> over I/O ... but that could have been different bars I suppose (it's so
> long ago that I can't remember).

Probably, it looks like it has both mmio and io:

drivers/scsi/sym53c8xx_2/sym_glue.c

#ifdef CONFIG_SCSI_SYM53C8XX_MMIO
        if (device->mmio_base)
                device->s.ioaddr = pci_iomap(pdev, 1,
                                                pci_resource_len(pdev, 1));
#endif
        if (!device->s.ioaddr)
                device->s.ioaddr = pci_iomap(pdev, 0,
                                                pci_resource_len(pdev, 0));


so ... ACK?

> 
> James
> 

-- 
MSt

  reply	other threads:[~2011-12-04 14:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1322163031.git.mst@redhat.com>
2011-11-24 20:15 ` [PATCH-RFC 01/10] lib: move GENERIC_IOMAP to lib/Kconfig Michael S. Tsirkin
2011-11-25  8:41   ` Jesper Nilsson
2011-11-28 20:12   ` Richard Kuo
2011-11-24 20:17 ` [PATCH-RFC 02/10] lib: add GENERIC_PCI_IOMAP Michael S. Tsirkin
2011-11-24 22:07   ` Arnd Bergmann
2011-11-25  0:54   ` Stephen Rothwell
2011-11-25  0:59     ` Stephen Rothwell
2011-11-27 17:12     ` Michael S. Tsirkin
2011-11-24 20:17 ` [PATCH-RFC 03/10] alpha: switch to GENERIC_PCI_IOMAP Michael S. Tsirkin
2011-11-24 20:17 ` [PATCH-RFC 04/10] arm: " Michael S. Tsirkin
2011-11-24 20:18 ` [PATCH-RFC 05/10] microblaze: " Michael S. Tsirkin
2011-11-24 20:18 ` [PATCH-RFC 06/10] mips: " Michael S. Tsirkin
2012-01-28 22:38   ` Kevin Cernekee
2012-01-29 22:45     ` Michael S. Tsirkin
2011-11-24 20:19 ` [PATCH-RFC 07/10] parisc: " Michael S. Tsirkin
2011-12-04 10:48   ` Michael S. Tsirkin
2011-12-04 14:22     ` James Bottomley
2011-12-04 14:30       ` Michael S. Tsirkin
2011-12-04 14:32         ` James Bottomley
2011-12-04 14:42           ` Michael S. Tsirkin [this message]
2011-12-05 15:33             ` James Bottomley
2011-12-05 16:24               ` Michael S. Tsirkin
2011-12-05 16:46                 ` James Bottomley
2011-12-05 18:23         ` Grant Grundler
2011-12-06 11:06           ` Michael S. Tsirkin
2011-12-06 16:18             ` Grant Grundler
2011-12-06 16:24               ` Michael S. Tsirkin
2011-12-16  2:11                 ` Grant Grundler
2011-11-24 20:19 ` [PATCH-RFC 08/10] powerpc: " Michael S. Tsirkin
2011-11-24 20:20 ` [PATCH-RFC 09/10] sh: " Michael S. Tsirkin
2011-11-24 20:21 ` [PATCH-RFC 10/10] sparc: " Michael S. Tsirkin

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=20111204144236.GA21506@redhat.com \
    --to=mst@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=deller@gmx.de \
    --cc=jejb@parisc-linux.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.org \
    /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).