From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
mingo@elte.hu, jeremy@goop.org, tony.luck@intel.com,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
x86@kernel.org, ian.campbell@citrix.com,
beckyb@kernel.crashing.org
Subject: Re: [PATCH 0 of 9] swiotlb: use phys_addr_t for pages
Date: Mon, 29 Dec 2008 08:37:44 +1100 [thread overview]
Message-ID: <1230500264.15389.3.camel@pasglop> (raw)
In-Reply-To: <20081228073012.GA30012@infradead.org>
On Sun, 2008-12-28 at 02:30 -0500, Christoph Hellwig wrote:
> Also the calgary iommu is very similar to those used on some pseries
> machines, but I'd have to look at the code if the interface actually
> still is similar, or if the PPC firmware adds too much abstractions
> inbetween.
Well, we have basically two backends... in the same file but they are
really different and I may split them one of these days. One is
"native", used in theory only on POWER4 (and internal bare-metal stuff)
and one is purely via hypervisor calls.
> Also the older IA64 altixens have a slightly updated version of the
> iommu used on MIPS IP27 (and the same as on MIPS IP35 which we'll
> hopefully support one day)
BTW. On a tangent here, but I do prefer in the long run switching DMA
ops mostly away from struct page * + offset and toward phys_addr_t (even
if we won't change the SG variant).
The reason is sneaky :-) But there are cases, especially in embedded
space, where it would be nice to be able to DMA to/from MMIO areas or in
general areas not covered by struct pages. Currently doing so requires
hacking all the way through the stack, it might be possible to do it
more nicely with arch custom DMA ops provided we can pass around
addresses an not struct page*.
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-28 21:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 18:26 [PATCH 0 of 9] swiotlb: use phys_addr_t for pages Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 1 of 9] revert "swiotlb: support bouncing of HighMem pages." Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 2 of 9] revert "swiotlb: factor out copy to/from device." Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 3 of 9] swiotlb: add hwdev to swiotlb_phys_to_bus Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 4 of 9] swiotlb: Drop SG_ENT_VIRT_ADDRESS macro Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 5 of 9] swiotlb: Rename SG_ENT_PHYS_ADDRESS to SG_ENT_BUS_ADDRESS Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 6 of 9] swiotlb: Store phys address in io_tlb_orig_addr array Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 7 of 9] swiotlb: Add support for systems with highmem Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 8 of 9] swiotlb: cleanups to swiotlb_bounce() Jeremy Fitzhardinge
2008-12-22 18:26 ` [PATCH 9 of 9] ia64/x86/swiotlb: use enum dma_data_direciton in dma_ops Jeremy Fitzhardinge
2008-12-22 18:43 ` [PATCH 0 of 9] swiotlb: use phys_addr_t for pages FUJITA Tomonori
2008-12-27 10:48 ` Ingo Molnar
2008-12-27 15:06 ` FUJITA Tomonori
2008-12-28 5:01 ` Jeremy Fitzhardinge
2008-12-28 9:50 ` Ingo Molnar
2008-12-27 16:44 ` FUJITA Tomonori
2008-12-27 16:56 ` Ingo Molnar
2008-12-27 17:03 ` FUJITA Tomonori
2008-12-28 5:29 ` FUJITA Tomonori
2008-12-28 7:30 ` Christoph Hellwig
2008-12-28 9:36 ` FUJITA Tomonori
2008-12-28 21:37 ` Benjamin Herrenschmidt [this message]
2008-12-28 9:37 ` Ingo Molnar
2008-12-28 10:02 ` FUJITA Tomonori
2008-12-28 10:34 ` Ingo Molnar
2008-12-28 11:00 ` FUJITA Tomonori
2008-12-28 11:56 ` Ingo Molnar
2008-12-28 12:34 ` FUJITA Tomonori
2008-12-28 12:49 ` Ingo Molnar
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=1230500264.15389.3.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=beckyb@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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