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/
Home Products Support Community News


RE: [Xen-ia64-devel] Re: [Xen-devel] XenLinux/IA64 domU forward port

To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>, "xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] Re: [Xen-devel] XenLinux/IA64 domU forward port
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Thu, 14 Feb 2008 16:17:05 +0800
Delivery-date: Thu, 14 Feb 2008 00:27:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080214070957.GA8464%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080207085042.GB4842%yamahata@xxxxxxxxxxxxx><1202420163.23562.178.camel@bling><20080208053949.GA7416%yamahata@xxxxxxxxxxxxx> <20080214070957.GA8464%yamahata@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Achu2Koc6w8iMVv7RJGb3uS+oSTPJAACIA1g
Thread-topic: [Xen-ia64-devel] Re: [Xen-devel] XenLinux/IA64 domU forward port
Great progress!

> Eddie, I haven't forgotten your discussion.
> I think it is necessary to get linux-ia64 people involved for
> the discussion. The concrete patch is needed.

Yes, so are you planing to push pv_ops based solution or
binary patching based solution? My basic understanding to
redhat's concern is that they want to adopt similar approach
in IA64 side together with X86, which uses pv_ops.

> Once I split the patch up, I'll post them to linux-ia64 so that we
> can start the discussion with them.
> My vague idea is as follows.
> - For neutral paravirtualization api, some kind of ABI is necessary.
> - It would need some kind of static calling convention.
> - Currently the nearest standard is PAL static calling convention.
>   So far I agree with you.
> - PAL static calling convention uses banked registers(r16-r31) as
>   arguments. However it would be suboptimal or unsuitable for
>   paravirtualization ABI. Static and non-banked registers are
>   desirable.(at least for Xen) so that r9-r11, r14-r15 are desirable.

We can't destroy non bank0 register in interrupt/exception handler
before memory based storage is involved to save/restore them. 
That is why I'd like to limit those parameters to bank0 registers.
For current Xen, it is using kind of C ABI (i.e. R8/R9), we can argu
if it is best, but should be easy to commodate both.

thx, eddue

Xen-ia64-devel mailing list