From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: x86 swiotlb questions
Date: Wed, 03 Jan 2007 09:32:30 +0000
Message-ID: <C1C128AE.6FFD%keir@xensource.com>
References: <459B64E8.76E4.0078.0@novell.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: <459B64E8.76E4.0078.0@novell.com>
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: Jan Beulich <jbeulich@novell.com>
Cc: muli@il.ibm.com, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org




On 3/1/07 07:10, "Jan Beulich" <jbeulich@novell.com> wrote:

>> 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...

Sounds reasonable, although KM_BOUNCE_READ is a misnomer (since we write to
the kmap as well as read from it).

 -- Keir