From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir@xensource.com>
Cc: muli@il.ibm.com, xen-devel@lists.xensource.com
Subject: Re: x86 swiotlb questions
Date: Wed, 03 Jan 2007 11:01:53 +0000 [thread overview]
Message-ID: <459B9B31.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C1C128AE.6FFD%keir@xensource.com>
>>> Keir Fraser <keir@xensource.com> 03.01.07 10:32 >>>
>On 3/1/07 07:10, "Jan Beulich" <jbeulich@novell.com> wrote:
>> 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).
... similar to the (mis-)use of it in the EDAC driver.
Jan
next prev parent reply other threads:[~2007-01-03 11:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 17:32 x86 swiotlb questions Jan Beulich
2006-12-30 17:47 ` Keir Fraser
2007-01-02 8:39 ` Jan Beulich
2007-01-03 7:10 ` Jan Beulich
2007-01-03 9:32 ` Keir Fraser
2007-01-03 11:01 ` Jan Beulich [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 16:20 Jan Beulich
2006-12-22 21:00 ` Herbert Xu
2006-12-23 9:48 ` Keir Fraser
2006-12-22 14:49 Jan Beulich
2006-12-25 4:50 ` Muli Ben-Yehuda
2006-12-25 10:20 ` Keir Fraser
2006-12-15 12:50 Jan Beulich
2006-12-15 13:35 ` Keir Fraser
2006-12-15 13:53 ` Jan Beulich
2006-12-15 14:03 ` Keir Fraser
2006-12-15 14:17 ` Jan Beulich
2006-12-15 14:19 ` Keir Fraser
2006-12-15 14:46 ` Jan Beulich
2006-12-15 16:47 ` Keir Fraser
2006-12-15 16:19 ` Alan
2006-12-18 7:44 ` Jan Beulich
2006-12-18 9:39 ` Keir Fraser
2006-12-19 12:48 ` Jan Beulich
2006-12-19 14:14 ` Keir Fraser
2006-12-19 14:39 ` Jan Beulich
2006-12-19 14:46 ` Keir Fraser
2006-12-19 17:07 ` Muli Ben-Yehuda
2006-12-20 16:40 ` Jan Beulich
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=459B9B31.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir@xensource.com \
--cc=muli@il.ibm.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.