From: Hollis Blanchard <hollisb@us.ibm.com>
To: Keir Fraser <keir@xensource.com>
Cc: Zachary Amsden <zach@vmware.com>,
Jimi Xenidis <jimix@watson.ibm.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Ian Pratt <ian.pratt@xensource.com>,
virtualization@lists.osdl.org, linux-kernel@vger.kernel.org,
Jan Beulich <JBeulich@novell.com>,
Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: Re: [patch 12/21] Xen-paravirt: Allocate and free vmalloc areas
Date: Fri, 16 Feb 2007 11:26:19 -0600 [thread overview]
Message-ID: <1171646779.20683.5.camel@basalt> (raw)
In-Reply-To: <C1FB9605.9988%keir@xensource.com>
On Fri, 2007-02-16 at 17:10 +0000, Keir Fraser wrote:
>
>
> On 16/2/07 16:46, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
>
> > Yes, that would work. Unfortunately that's i386 arch-specific, whereas
> > the rest of this code is generic. I guess I could just move it all to
> > arch/i386/mm.
>
> This whole thing isn't an issue on ia64 (they no-op lock_vm_area) and
> powerpc doesn't use any of the Xen driver code at this time.
Not sure what you mean? PowerPC uses pretty much all of the Xen driver
code: event channels, blkfront/back, netfront/back, console, etc.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2007-02-16 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C1FB9605.9988%keir@xensource.com>
2007-02-16 17:12 ` [Xen-devel] Re: [patch 12/21] Xen-paravirt: Allocate and free vmalloc areas Keir Fraser
2007-02-16 17:12 ` Keir Fraser
2007-02-16 17:26 ` Hollis Blanchard [this message]
[not found] <C1FBB152.99B0%keir@xensource.com>
2007-02-16 19:19 ` Keir Fraser
2007-02-16 19:26 ` Jeremy Fitzhardinge
2007-02-16 23:29 ` Keir Fraser
2007-02-16 23:41 ` Jeremy Fitzhardinge
[not found] <C1FB967F.998B%keir@xensource.com>
2007-02-16 17:27 ` Jeremy Fitzhardinge
[not found] <C1FB4190.98FA%keir@xensource.com>
2007-02-16 11:34 ` Andi Kleen
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=1171646779.20683.5.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=JBeulich@novell.com \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=ian.pratt@xensource.com \
--cc=jeremy@goop.org \
--cc=jimix@watson.ibm.com \
--cc=keir@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.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).