From: James Bottomley <James.Bottomley@SteelEye.com>
To: David Miller <davem@davemloft.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Proposals to change the way all drivers work with SCSI commands
Date: Fri, 11 May 2007 16:36:56 -0500 [thread overview]
Message-ID: <1178919416.3692.82.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070511.142111.118971174.davem@davemloft.net>
On Fri, 2007-05-11 at 14:21 -0700, David Miller wrote:
> From: James Bottomley <James.Bottomley@SteelEye.com>
> Date: Fri, 11 May 2007 16:12:47 -0500
>
> > I could probably cook up a patch for you, if you like? ... I've already
> > done it for several other architectures.
>
> I don't want to use that "if (bus == &sbus_bus_type)" scheme so
> if that's what your patch will do don't bother :-)
That's sort of what you already have, if you're still using the generic
dma-mapping.h helpers in asm-sparc64. They already have a
BUG_ON(dev->bus != &pci_bus_type)
> I'm consolidating all of the IOMMU handling code on sparc64
> since they all do exactly the same thing, so at least on
> sparc64 there will be essentially direct calls to the IOMMU
> code agnostic of bus type.
OK ... I'll let you fix it.
On PARISC, we actually use a table of function pointers, but then we
also have several other oddities including having to walk up the bus
tree to find our IOMMU (having several) which can actually be on a
different bus type for some of the older systems (i.e. the PCI iommu is
in the GSC bus etc).
> Sparc32 will be a bit different, and that platform has no
> active maintainer so it'll have to wait until I have a
> spare weekend to do nothing but sparc32 stuff :-)
James
next prev parent reply other threads:[~2007-05-11 21:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 18:33 Proposals to change the way all drivers work with SCSI commands James Bottomley
2007-05-11 18:42 ` FUJITA Tomonori
2007-05-11 19:15 ` Jeff Garzik
2007-05-11 19:49 ` James Bottomley
2007-05-11 20:10 ` Jeff Garzik
2007-05-11 20:00 ` David Miller
2007-05-11 21:12 ` James Bottomley
2007-05-11 21:21 ` David Miller
2007-05-11 21:36 ` James Bottomley [this message]
2007-05-11 21:47 ` David Miller
2007-05-11 21:52 ` James Bottomley
2007-05-11 21:20 ` Stefan Richter
2007-05-11 21:30 ` Kristian Høgsberg
2007-05-11 21:58 ` Stefan Richter
2007-05-12 6:35 ` Muli Ben-Yehuda
2007-05-12 9:12 ` Heiko Carstens
2007-05-12 13:04 ` James Bottomley
2007-05-12 15:29 ` Christoph Hellwig
2007-05-12 15:50 ` James Bottomley
2007-05-12 15:52 ` Christoph Hellwig
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=1178919416.3692.82.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=davem@davemloft.net \
--cc=linux-scsi@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