From: Arjan van de Ven <arjan@infradead.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Christoph Hellwig <hch@lst.de>,
tony.luck@intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [IA64] swiotlb abstraction (e.g. for Xen)
Date: Tue, 13 Feb 2007 08:53:41 +0100 [thread overview]
Message-ID: <1171353226.12771.39.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <45D17660.76E4.0078.0@novell.com>
On Tue, 2007-02-13 at 07:27 +0000, Jan Beulich wrote:
> >>> Christoph Hellwig <hch@lst.de> 12.02.07 18:12 >>>
> >On Mon, Feb 12, 2007 at 07:30:55AM +0000, Jan Beulich wrote:
> >>
> >> As the topic says - the goal is to support Xen. But yes, I was afraid someone would
> >> claim this make the code look ugly. And no, I currently don't have ideas to address
> >> any of your comments without breaking functionality on Xen...
> >
> >We don't have Xen merged, and it doesn't look like we're going to get it
> >soon. Also the code is only for dom0 which will take even longer.
> >At this point I'm pretty sure the code is cleaner, simpler and easier to
> >maintain if you just split out a xendom0swiotlb instead of messing up
> >the existing code.
>
> We have such a file, and the purpose of the patch was to get rid of it.
but the result is butt-ugly... please don't do that... that code is..
interesting enough already without all the junk added to it
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
prev parent reply other threads:[~2007-02-13 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702070759.l177xIti030295@hera.kernel.org>
2007-02-07 8:32 ` [IA64] swiotlb abstraction (e.g. for Xen) Christoph Hellwig
2007-02-11 7:25 ` Christoph Hellwig
2007-02-12 7:30 ` Jan Beulich
2007-02-12 8:14 ` Arjan van de Ven
2007-02-12 8:56 ` Muli Ben-Yehuda
2007-02-12 8:58 ` Jan Beulich
2007-02-12 17:12 ` Christoph Hellwig
2007-02-13 7:27 ` Jan Beulich
2007-02-13 7:53 ` Arjan van de Ven [this message]
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=1171353226.12771.39.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=hch@lst.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).