From: olof@lixom.net (Olof Johansson)
To: Christoph Hellwig <hch@lst.de>
Cc: paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] DMA 4GB boundary protection
Date: Sat, 3 Mar 2007 23:52:21 -0600 [thread overview]
Message-ID: <20070304055221.GA11982@lixom.net> (raw)
In-Reply-To: <20070304051738.GA30747@lst.de>
On Sun, Mar 04, 2007 at 06:17:38AM +0100, Christoph Hellwig wrote:
> On Sat, Mar 03, 2007 at 09:27:31AM +0100, Benjamin Herrenschmidt wrote:
> > - Drivers are broken -today- and I doubt they can all be audited and
> > fixed (and fixes bacported to distros) quickly
>
> Which drivers? All requests coming from the block layer make sure
> you never span the 4GB boundary, and IIRC that same is true for
> networking. Similarly dma_alloc_coherent and pci_alloc_consinstant
> only allocate from the lower 4G unless told otherwise.
Since the IOMMU layer adds a completely independent address space, any
mapping might end up straddling the boundary if you're unlucky. But, with
the above info, adding the restrictions in the iommu code seems safer --
at least it won't cause problems on non-translated enviromnents if the
block and network code makes sure it can't happen there.
> A driver writer
> would have to be extra-ordinarily stuid to get this wrong. (And yes,
> some driver writers are..)
Any pci_map_single or friends should be able to end up there based on
how the iommu allocator works. It doesn't take into consideration any
kind of alignment of the physical regions being mapped.
-Olof
next prev parent reply other threads:[~2007-03-04 5:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 21:49 [PATCH] DMA 4GB boundary protection Jake Moilanen
2007-03-02 22:27 ` Olof Johansson
2007-03-03 8:27 ` Benjamin Herrenschmidt
2007-03-03 23:25 ` Olof Johansson
2007-03-04 5:17 ` Christoph Hellwig
2007-03-04 5:52 ` Olof Johansson [this message]
2007-03-03 23:29 ` Olof Johansson
2007-03-03 23:32 ` Segher Boessenkool
2007-03-03 23:57 ` Olof Johansson
2007-03-21 21:05 ` Jake Moilanen
2007-03-21 21:39 ` Olof Johansson
2007-03-22 17:53 ` Olof Johansson
2007-03-22 17:47 ` Jake Moilanen
2007-03-22 22:52 ` Segher Boessenkool
2007-03-27 20:10 ` Jake Moilanen
2007-03-27 20:55 ` Benjamin Herrenschmidt
2007-03-27 23:48 ` Paul Mackerras
2007-03-28 15:56 ` Olof Johansson
2007-03-28 18:17 ` Jake Moilanen
2007-03-28 23:23 ` Benjamin Herrenschmidt
2007-03-29 13:44 ` Jake Moilanen
2007-03-29 14:52 ` Olof Johansson
2007-03-29 21:54 ` Benjamin Herrenschmidt
2007-04-23 12:22 ` Paul Mackerras
2007-04-24 3:07 ` Olof Johansson
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=20070304055221.GA11982@lixom.net \
--to=olof@lixom.net \
--cc=hch@lst.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).