From: richard.brunner@amd.com
To: linux-kernel@vger.kernel.org
Subject: RE: IOMMUs was Re: Intel vs AMD x86-64
Date: Tue, 24 Feb 2004 09:50:02 -0600 [thread overview]
Message-ID: <99F2150714F93F448942F9A9F112634C0FD384E3@txexmtae.amd.com> (raw)
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> On Opteron the IOMMU code (ab)uses the built in AGPv3 GART in
> the CPU, which
> was originally intended for AGP. AMD converted it to be able
> to remap PCI especially for Linux, which I think deserves applause.
>
> It works surprisingly well even though it was not designed as
> a real IOMMU. Of course one of the main advantages of a real
> IOMMU - preventing arbitary memory corruption from broken
> devices - is lost because the remapping table is just a hole
> in the memory. I'm
> secretly hoping that when there is more support for Linux at
> chipset vendors they will someday add a bit to isolate all
> traffic that doesn't go through the GART from the main
> memory. This way you could get a much more reliable system
> that can tolerate broken PCI devices at a moderate
> performance penalty.
Andi is being modest. It was he and Andrea Arcangeli who convinced
me we had a problem. We found a way to trick the AGP
GART hardware into helping, and then they turned it into a
"real" solution and helped us work the warts out of the BIOS
to enable it.
next reply other threads:[~2004-02-24 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 15:50 richard.brunner [this message]
2004-02-24 16:27 ` Mike Fedyk
[not found] <Pine.LNX.4.44.0402231625220.9708-100000@chimarrao.boston.redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.58.0402231335430.3005@ppc970.osdl.org.suse.lists.linux.kernel>
[not found] ` <20040223134853.5947a414.davem@redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.58.0402231359280.3005@ppc970.osdl.org.suse.lists.linux.kernel>
2004-02-24 14:06 ` Andi Kleen
2004-02-24 18:13 ` David S. Miller
2004-02-27 1:28 ` Andi Kleen
2004-02-24 18:41 ` David S. Miller
2004-02-25 0:36 ` Benjamin Herrenschmidt
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=99F2150714F93F448942F9A9F112634C0FD384E3@txexmtae.amd.com \
--to=richard.brunner@amd.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®