From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Airlie <airlied@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Keir Fraser <kier.fraser@eu.citrix.com>,
xen-devel@lists.xensource.com,
Joerg Roedel <joerg.roedel@amd.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Zhenyu Wang <zhenyu.z.wang@intel.com>
Subject: Re: [Xen-devel] Re: [RFC] Make AGP work with IOMMU
Date: Wed, 05 Aug 2009 11:26:52 -0700 [thread overview]
Message-ID: <4A79CEEC.9030008@goop.org> (raw)
In-Reply-To: <21d7e9970908042357m6080e88fyeaaad171888766f2@mail.gmail.com>
On 08/04/09 23:57, Dave Airlie wrote:
>> All we've done so far is make intel-agp use the DMA API correctly. And
>> that's conditional on CONFIG_DMAR. But we could make it unconditional,
>> and make the other drivers do it too. The code is all fairly generic.
>>
>> Without an IOMMU, the overhead would be fairly minimal.
>>
>>
>
> I'm not sure how prevalent Xen is on AGP systems, I'm going to guess
> not enough that anyone cares.
What do you mean by AGP here? Do you mean "machine with physical AGP
port", or "machine with graphics using the AGP aperature"? There's an
increasing interest in putting Xen on desktop machines, so the former is
debatable, but the latter (I think?) definitely isn't true.
> Intel integrated chips are the only AGP
> codebase user that are made any more, and they don't really use AGP
> its just a legacy of the previous designs.
>
>
Plenty of people are using older machines for testing, etc, so I
wouldn't want to exclude them too lightly. I've got bug reports from
people using older Radeons, etc.
J
next prev parent reply other threads:[~2009-08-05 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 15:04 [RFC] Make AGP work with IOMMU David Woodhouse
2009-07-29 6:28 ` Dave Airlie
2009-07-29 7:15 ` David Woodhouse
2009-07-29 8:43 ` Dave Airlie
2009-07-29 9:01 ` David Woodhouse
2009-07-29 9:36 ` David Woodhouse
2009-08-03 6:50 ` Zhenyu Wang
2009-08-03 8:39 ` David Woodhouse
2009-08-04 23:52 ` [Xen-devel] " Jeremy Fitzhardinge
2009-08-05 6:44 ` David Woodhouse
2009-08-05 6:57 ` Dave Airlie
2009-08-05 7:08 ` David Woodhouse
2009-08-05 18:26 ` Jeremy Fitzhardinge [this message]
2009-08-05 23:12 ` Dave Airlie
2009-08-06 19:32 ` Jeremy Fitzhardinge
2009-08-06 19:36 ` David Woodhouse
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=4A79CEEC.9030008@goop.org \
--to=jeremy@goop.org \
--cc=airlied@gmail.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=kier.fraser@eu.citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=zhenyu.z.wang@intel.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