WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] x86/amd64 vs IA64

To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] x86/amd64 vs IA64
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Tue, 2 Jun 2009 20:38:48 +1000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 02 Jun 2009 03:39:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090602073054.GF9176%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D016DD562@trantor> <20090602073054.GF9176%yamahata@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnjVDVGxVmY8VNbQxyLMsDEPv91WQAGgTuA
Thread-topic: [Xen-devel] x86/amd64 vs IA64
Thankyou very much for the information provided below. I'll make my way
through it over the next few days.

James

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Isaku Yamahata
> Sent: Tuesday, 2 June 2009 17:31
> To: James Harper
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] x86/amd64 vs IA64
> 
> On Tue, Jun 02, 2009 at 12:26:39PM +1000, James Harper wrote:
> > How different is IA64 to x86/amd64 in terms of hypercalls and
> > platform_pci setup under HVM?
> >
> > I'm having a look at what is involved in porting GPLPV drivers for
> > Windows to IA64.
> >
> > I can't even seem to find where the HYPERCALL_ functions/macros are
> > defined!
> 
> Hi. I'm glad to hear that.
> Linux unmodified drivers are supported on ia64, so it's quite
> possible to port GPLPV to IA64 windows, I suppose.
> If you need any help, don't hesitate to ask.
> 
> Probably the file you want to see would be
>       linux-2.6.18-xen.hg/include/asm-ia64/hypercall.h
> which defines HYPERVISOR_xxx() functions.
> Eventually __hypercall() in
linux-2.6.18-xen.hg/arch/ia64/xen/hypercall.S
> issues hypercall. "break 0x1000" is the instruction.
> 0x1000 is arbitrarily selected constant for hypercall ABI between
> guest kernel and xen VMM.
> 
> The most difference is the way to pass arguments.
> On x86, arguments are passed by guest virtual address.
> On the other hand they are passed by guest physical address.
> So when issuing hypercall with arguments, arguments in virtual address
> must be converted into guest physical address. Such stubs are called
> xencomm.
> You can see some of HYPERVISOR_xxx are replaced with
xencomm_hypercall_xxx
> which does such conversions.
> 
> Maybe at first xencomm routines should be ported for hypercall.
> linux-2.6.18-xen.hg/drivers/xen/core/xencomm.c and
> linux-2.6.18-xen.hg/arch/ia64/xen/xencomm.c
> I suppose the conversion function from virtual address to guest
> physical address would needs rewrite for ia64 windows.
> 
> 
> The followings are related files which you might want to see.
> 
> ifeq ($(ARCH),ia64)
>   xen-platform-pci-objs += xencomm.o xencomm_arch.o xcom_hcall.o
xcom_asm.o
> endif
> in xen-unstable.hg/unmodified_drivers/linux-2.6/platform-pci/Kbuild
> 
> The files related to hypercall are
> linux-2.6.18-xen.hg/
>       arch/ia64/xen/
>               xcom_hcall.c
>               xcom_privcmd.c
>               xcom_asm.S
>               xencomm.c
>       drivers/xen/core/
>               xencomm.c
> 
> thanks,
> --
> yamahata
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>