[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1242992766.22654.279.camel@zakaz.uk.xensource.com>
Date: Fri, 22 May 2009 12:46:06 +0100
From: Ian Campbell <Ian.Campbell@...citrix.com>
To: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
CC: "jeremy@...p.org" <jeremy@...p.org>,
"beckyb@...nel.crashing.org" <beckyb@...nel.crashing.org>,
"okir@...e.de" <okir@...e.de>, "mingo@...e.hu" <mingo@...e.hu>,
"gregkh@...e.de" <gregkh@...e.de>,
"xendevel@...ts.xensource.com" <xendevel@...ts.xensource.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] swiotlb: make swiotlb allocation functions
architecture-specific
On Fri, 2009-05-22 at 07:13 -0400, FUJITA Tomonori wrote:
> On Thu, 21 May 2009 17:15:25 +0100
> Ian Campbell <ian.campbell@...rix.com> wrote:
>
> > Some architectures need to allocate memory to be used as a swiotlb in
> > a special manner.
>
> Hmm, what architectures need a special manner? I guess only Xen.
The x86 architecture, when running as a paravirtualised guest under Xen,
needs it. I guess ia64 might need it for similar reasons, I'm not sure.
How does the fact that x86-Xen is (currently) the only user invalidate
the requirement? You seem to have a knee-jerk reaction to anything which
might be useful to Xen and I really don't understand why that should be
the case.
We are talking about an initialisation path and we are not talking about
changes which completely obscure all meaning or anything. The semantics
of the API are pretty clear, I think.
Ian.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists