From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: Re: x86 swiotlb questions
Date: Wed, 03 Jan 2007 07:10:16 +0000
Message-ID: <459B64E8.76E4.0078.0@novell.com>
References: <4596A2C9020000780002B284@public.id2-vpn.continvity.gns.novell.com>
	<C1BC56A5.6870%keir@xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C1BC56A5.6870%keir@xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir.Fraser@cl.cam.ac.uk
Cc: muli@il.ibm.com, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

>Here's a thought: if the highmem DMA requests come from *only* the blkdev
>subsystem, then perhaps we could use its highmem bounce buffer (I think that
>still exists?).

Another, only partially related thought: The addition of KM_SWIOTLB is the only
difference to native kmap_types.h. It would seem to me that, at the price of
disabling interrupts around the use, it should be possible to replace that with
KM_BOUNCE_READ and let go of the Xen specific header...

Jan