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: ATI radeon fails with "iommu=soft swiotlb=force" (se

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: ATI radeon fails with "iommu=soft swiotlb=force" (seen on RV730/RV740 and RS780/RS800)
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 05 Oct 2009 12:12:23 -0700
Cc: dri-devel@xxxxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Mon, 05 Oct 2009 12:12:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091005143756.GA3681@xxxxxxxxxxxxxxxxxxx>
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: <41093.83224.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4AC649B0.5090700@xxxxxxxx> <4AC9E75F0200007800017F61@xxxxxxxxxxxxxxxxxx> <20091005140152.GA3127@xxxxxxxxxxxxxxxxxxx> <20091005143756.GA3681@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 10/05/09 07:37, Konrad Rzeszutek Wilk wrote:
> Jeremy suggested another one. That is for the Xen IOMMU to fix the virtual
> mappings. Meaning we would swipe out the virtual address of the page to point
> to a virtual address (along with returning an 32-bit bus address) under the 
> 4GB mark.
> That involves also changing the mappings of the old virtual address to the 
> new one
> where ever it may be.
>
> Jeremy, did I get that right?
>   

Yeah.  We'd make xen_dma_map_page() use xen_exchange_memory to replace
the underlying page with something matching the device's requirements. 
That would be fairly straightforward for kernel and vmapped pages, but
it gets pretty complex if the page is mapped into userspace (partly
because of the need to use rmap to find all the user mappings, and
partly because I don't know what the locking/atomicity requirements
would be).

    J


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

<Prev in Thread] Current Thread [Next in Thread>