From: Hollis Blanchard <hollisb@us.ibm.com>
To: Tristan Gingold <tgingold@free.fr>
Cc: xen-ia64-devel@lists.xensource.com,
xen-devel@lists.xensource.com,
Alex Williamson <alex.williamson@hp.com>,
xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: [XenPPC] Re: consolidated xencomm
Date: Thu, 16 Nov 2006 18:14:59 -0600 [thread overview]
Message-ID: <1163722499.26011.131.camel@basalt> (raw)
In-Reply-To: <1163713977.26011.74.camel@basalt>
On Thu, 2006-11-16 at 15:52 -0600, Hollis Blanchard wrote:
>
> The patch I cited earlier today is a bug fix that applies to PowerPC
> as well, but the code is not shared, and the patch did not fix both
> architectures.
First let me apologize for getting annoyed. I was wrong on a couple
fronts:
- Yamahata-san has in fact patched PowerPC's usercopy.c to fix bugs
along with IA64.
- This particular patch was not needed on PowerPC at all.
Also, I didn't realize Tristan was leaving Bull, so I can understand the
motivation to check something in short-term and sort it out later.
This patch was a surprise to me because I hadn't realized that IA64 had
in fact forked xencomm, and I did a fair amount of work in the PPC tree
to support IA64 and never got feedback on it. (That must have been about
the time Tristan left.) Here is my original mail on the subject.
(Strangely I can't find it in the xen-ia64-devel archives.)
> Subject: xencomm porting and "inline" handles
> From: Hollis Blanchard <hollisb@us.ibm.com>
> To: Tristan Gingold <Tristan.Gingold@bull.net>
> Cc: xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
> Message-Id: <1158086273.14752.53.camel@basalt.austin.ibm.com>
> Date: Tue, 12 Sep 2006 13:37:54 -0500
[snip]
> The Xen changes are committed to xenppc-unstable.hg . In Xen,
> architectures need to provide:
> - XENCOMM_INLINE_FLAG in arch-foo.h
> - paddr_to_maddr(). I'm open to alternative names, but a standard
> function seems useful outside xencomm. (I wish we had one for Linux.)
> - asm/guest_access.h that just #includes xen/xencomm.h
>
> Once you have IA64-specific implementations for the above, I will
> submit the whole thing to xen-devel. (Note that Linux doesn't actually
> have to use it right now; it won't break anything.)
>
> The Linux are committed to linux-ppc-2.6.hg . I think for Linux
> architectures just need to supply:
> - XENCOMM_INLINE_FLAG in arch-foo.h
> - xencomm_vtop()
[snip]
This work is still present in
http://xenbits.xensource.com/ext/xenppc-unstable.hg , and I would
appreciate comments about getting this code shared.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2006-11-17 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Gk8pJ-0007ef-Tr@xenbits.xensource.com>
2006-11-16 15:55 ` [Xen-changelog] [xen-unstable] [IA64] fix xencomm_handle_is_null() Hollis Blanchard
2006-11-16 18:08 ` Alex Williamson
2006-11-16 20:44 ` Re: [Xen-devel] " Tristan Gingold
2006-11-16 21:52 ` consolidated xencomm Hollis Blanchard
2006-11-17 0:14 ` Hollis Blanchard [this message]
2006-11-16 21:58 ` Hollis Blanchard
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=1163722499.26011.131.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=alex.williamson@hp.com \
--cc=tgingold@free.fr \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xen-ppc-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.