WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [RFC] Make AGP work with IOMMU

To: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [RFC] Make AGP work with IOMMU
From: Dave Airlie <airlied@xxxxxxxxx>
Date: Wed, 5 Aug 2009 16:57:51 +1000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Zhenyu Wang <zhenyu.z.wang@xxxxxxxxx>, Joerg Roedel <joerg.roedel@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx, Keir Fraser <kier.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 05 Aug 2009 05:44:24 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5skAcwrqBcgxOZxdeahNTpaN/loVB2N8V4leO4v3FXc=; b=qobvbp2Z2rXRd3K49MGLuSu4XpSrVUQEf52v3BWt1agzK2Ve6yRhlZ8pWb6vCbXZZs AvPaYvmknMu3UK+Tr56N5QljvIASpECXdLcq/QvceFYUFWmg7Bwy0Quvkx0xsM4+qLh2 hLJ5G/cetGkj3R9blFNAw+kA8iBNM53XG/Al0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dAN36slg6zE6GChHr1Gn+0JX/fdEiHV6AFh9BGa2Taftq13Ftyoqv3c1PlyRRDsVr3 8RWA+152Z6WNVeGapqjE3zBhlZFsXymS2CbkzxoWrvL+JhvCCtX3CviTAMh0gWOGAABj JSpV+ZLJ3gE8jAptFt3UOIq8dOT1B6BEUXVgE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1249454696.9324.325.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1248707041.6100.35.camel@xxxxxxxxxxxxxxxxxxxxx> <21d7e9970907282328l4a44b9a2of4500c5c84a3586b@xxxxxxxxxxxxxx> <1248851712.19733.214.camel@xxxxxxxxxxxxxxxxxxxxx> <21d7e9970907290143q6778511cvda1c6b915f61654a@xxxxxxxxxxxxxx> <1248860205.19733.238.camel@xxxxxxxxxxxxxxxxxxxxx> <4A78C9C6.6010103@xxxxxxxx> <1249454696.9324.325.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Aug 5, 2009 at 4:44 PM, David Woodhouse<dwmw2@xxxxxxxxxxxxx> wrote:
> On Tue, 2009-08-04 at 16:52 -0700, Jeremy Fitzhardinge wrote:
>> And just when I have patches to use them for their original purpose...
>>
>> Looking back over the thread, are you saying that most users are already
>> using the DMA API correctly for AGP accesses?  If that's true then we
>> should be just fine.
>
> No, not 'most users'. But perhaps we should.
>
> 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. 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.

Dave.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel