[XenPPC] Re: xencomm porting and inline handles

2006-09-29 Thread Tristan Gingold
Le Jeudi 28 Septembre 2006 17:07, Hollis Blanchard a écrit : On Thu, 2006-09-28 at 08:27 +0200, Tristan Gingold wrote: Le Mercredi 27 Septembre 2006 17:10, Hollis Blanchard a écrit : On Wed, 2006-09-27 at 08:19 +0200, Tristan Gingold wrote: Le Mardi 26 Septembre 2006 20:23, Hollis

[XenPPC] Re: xencomm porting and inline handles

2006-09-28 Thread Tristan Gingold
Le Mercredi 27 Septembre 2006 17:10, Hollis Blanchard a écrit : On Wed, 2006-09-27 at 08:19 +0200, Tristan Gingold wrote: Le Mardi 26 Septembre 2006 20:23, Hollis Blanchard a écrit : On Tue, 2006-09-26 at 10:04 +0200, Tristan Gingold wrote: After more work, inline xencomm

[XenPPC] Re: xencomm porting and inline handles

2006-09-27 Thread Tristan Gingold
Le Mardi 26 Septembre 2006 20:23, Hollis Blanchard a écrit : On Tue, 2006-09-26 at 10:04 +0200, Tristan Gingold wrote: After more work, inline xencomm is not that magic: it doesn't work for modules which are loaded in virtual memory. So I have to use mini xencomm at least for modules

[XenPPC] Re: xencomm porting and inline handles

2006-09-26 Thread Tristan Gingold
Le Mardi 12 Septembre 2006 20:37, Hollis Blanchard a écrit : Hi Tristan, I've just implemented your inline handle idea. 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

Re: [Xen-devel] Re: [XenPPC] [RFC][PATCH] Isolating ACM's architecture-dependent parts

2006-09-26 Thread Tristan Gingold
Le Mardi 26 Septembre 2006 13:56, Stefan Berger a écrit : Tristan Gingold [EMAIL PROTECTED] wrote on 09/26/2006 07:54:27 [...] Hi, sorry for the late reply, I am just back from holidays. It seems you patch has not yet been merged. Is there any reason ? I'd like to see

[XenPPC] Re: [Xen-devel] RFC: xencomm in common

2006-08-24 Thread Tristan Gingold
Le Jeudi 24 Août 2006 03:44, Isaku Yamahata a écrit : Hi Tristan. Since I looked the patch very roughly, I might be wrong and parania though. xencomm_copy_from_guest(), xencomm_copy_to_guest() converts address, then acessses a page. The Xen/IA64 P2M table is lockless so that the page can be

Re: [XenPPC] PATCH: xencomm - kernel side

2006-08-24 Thread Tristan Gingold
Le Mercredi 23 Août 2006 18:39, Hollis Blanchard a écrit : On Wed, 2006-08-23 at 14:31 +0200, Tristan Gingold wrote: taking into account Hollis comments I now submit this patch. IA64 specific stuff will be posted to xen-ia64-unstable after merge. NAK pending outcome of other comments

[XenPPC] Re: [Xen-devel] RFC: xencomm in common

2006-08-23 Thread Tristan Gingold
Le Lundi 21 Août 2006 11:41, Keir Fraser a écrit : On 21/8/06 10:20 am, Tristan Gingold [EMAIL PROTECTED] wrote: Fine in principle. Specific comments: * powerpc should be cleaned up at the same time to use the common infrastructure. I don't want duplicated code hanging around in arch

[XenPPC] PATCH: xencomm - kernel side

2006-08-23 Thread Tristan Gingold
Xencomm support in linux kernel: * descriptor creation and destruction * transformation of kernels hypercalls * transformation of privcmd issued hypercalls. It must be enabled by architecture config. Signed-off-by: Tristan Gingold [EMAIL PROTECTED] Signed-off-by: Hollis Blanchard [EMAIL PROTECTED

Re: [Xen-devel] Re: [XenPPC] Xencomm for xen/ia64

2006-08-22 Thread Tristan Gingold
Le Lundi 21 Août 2006 18:24, Hollis Blanchard a écrit : On Mon, 2006-08-21 at 08:46 +0200, Tristan Gingold wrote: Le Vendredi 18 Août 2006 18:39, Hollis Blanchard a écrit : On Fri, 2006-08-18 at 11:04 +0200, Tristan Gingold wrote: Le Jeudi 17 Août 2006 20:35, Hollis Blanchard a écrit

Re: [XenPPC] RFC: xencomm - linux side

2006-08-22 Thread Tristan Gingold
Le Lundi 21 Août 2006 21:07, Hollis Blanchard a écrit : On Mon, 2006-08-21 at 17:18 +0200, Tristan Gingold wrote: I am posting the linux xencomm code for review. I'd plan to submit soon unless comments/remarks. NAK. I'm still waiting to hear back about how you can use xencomm_inline

Re: [Xen-devel] Re: [XenPPC] Xencomm for xen/ia64

2006-08-21 Thread Tristan Gingold
Le Vendredi 18 Août 2006 18:39, Hollis Blanchard a écrit : On Fri, 2006-08-18 at 11:04 +0200, Tristan Gingold wrote: Le Jeudi 17 Août 2006 20:35, Hollis Blanchard a écrit : If we agree on using xencomm we will have to work with xen/ppc people in order not to duplicate the code

Re: [XenPPC] Xencomm on ia64 - The patches

2006-08-21 Thread Tristan Gingold
Le Vendredi 18 Août 2006 23:21, Hollis Blanchard a écrit : On Fri, 2006-08-18 at 18:02 +0200, Tristan Gingold wrote: these are the patches to port xencomm on ia64. This is just an RFC. I have to clean-up the code so that it could be shared between ia64 and ppc. Great! Your patches were

Re: [XenPPC] Xencomm on ia64 - The patches

2006-08-21 Thread Tristan Gingold
Le Vendredi 18 Août 2006 23:21, Hollis Blanchard a écrit : On Fri, 2006-08-18 at 18:02 +0200, Tristan Gingold wrote: [...] I have also fixed a few bugs in guest_access.h Do you think you could split those out as a diff to xen/include/asm-powerpc/guest_access.h, to be applied before we move

Re: [XenPPC] Xencomm on ia64 - The patches

2006-08-21 Thread Tristan Gingold
Le Lundi 21 Août 2006 13:13, Jimi Xenidis a écrit : On Aug 21, 2006, at 3:47 AM, Tristan Gingold wrote: Le Vendredi 18 Août 2006 23:21, Hollis Blanchard a écrit : On Fri, 2006-08-18 at 18:02 +0200, Tristan Gingold wrote: [...] I have also fixed a few bugs in guest_access.h Do you

[XenPPC] Xencomm on ia64 - The patches

2006-08-18 Thread Tristan Gingold
Hi, these are the patches to port xencomm on ia64. This is just an RFC. I have to clean-up the code so that it could be shared between ia64 and ppc. I have added the xencomm_inline feature which makes (IMHO) hcall.c more readable and safer (particularly at boot time). Wether or not

[XenPPC] Xencomm for xen/ia64

2006-08-16 Thread Tristan Gingold
Hi, [xen-ppc-devel is on CC just for info] I am porting xen-ppc's xencomm to xen/ia64. Currently on xen/ia64 copy_from/to_guest uses guest virtual address. This works well as long as the virtual addresses are in the TLB. When not in TLB (or vTLB) the hypercall can't success without domain