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-ia64-devel

[Xen-ia64-devel] Re: [Xen-devel] [RFC][PATCH]mini-os: big-endian mini-os

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Re: [Xen-devel] [RFC][PATCH]mini-os: big-endian mini-os on ia64
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 27 Feb 2007 10:55:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Grzegorz Milos <gm281@xxxxxxxxx>, Xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Feb 2007 01:54:50 -0800
Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=EI9/5X5h/279CaqSAFBa32QeBAv0F+X1BcYPmHYWzF/hGrhz3RWlS/3rQi4HHVwOet59Ku27v6LDgAFlsJMmxDo1tKKxUY9jbBFRo5O8yaFZ+1d1TylHNNoBJT7C2GDW;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C201FEEB.9D89%keir@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: <C201FEEB.9D89%keir@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
Am Mittwoch, 21. Februar 2007 14:51 schrieb Keir Fraser:
> On 21/2/07 13:04, "Dietmar Hahn" <dietmar.hahn@xxxxxxxxxxxxxxxxxxx> wrote:
> > I think the SWAP()'s are not that much. Maybe I can reduce this by moving
> > some into the ia64-hypercall interface. What remain are the accesses to
> > the ring buffers (not that simple in netfront because of the xen-macros).
> > Perhaps some other guys contribute their opinion.
>
> I would actually argue that they're scattered all over the place and it
> will be hard to be sure that we have all the SWAPs we need and only the
> SWAPs we need. Particularly to continue ensuring that given that most
> development will be with minios having same endianness as Xen.
>
> In short: it's ugly and unless someone really cares it will rot.
>
>  -- Keir

Now that the environment (libxc, xen-ia64) is ready to start a simple BE domU, 
I want to start a new discussion about BE able mini-os.
What I want to have is a mini-os, where everybody whith ia64 hardware can 
build and run a BE mini-os beside LE mini-os (or other domU's) on xen-ia64 
hypervisor. If you say at this point: no interrest for such a thing, than we 
can stop this discussion here.
On the other side we should discuss how this can be realized.
My target with the first patch was to minimize the impact on common mini-os 
source as small as possible and that the hypervisor shouldn't be touched by 
BE/LE problematic. Therewidth I did only the SWAPs at the right place in the 
mini-os. Maybe that SWAPs are ugly but the SWAPs have to be done somewhere 
and the best place in my opinion is in the domU at the lowest level functions 
on top of the hypervisor interface - in gnttab, xenbus, xencons, event.
The other way would be building wrappers around all the accesses to 
domU/hypervisor interfaces and hide the SWAPs there. But this seems a little 
bit overkill at this stage.
Oh and yes I will care about this in the mini-os!
Thanks.

Dietmar

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