[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-ia64-devel] Support big endian domU's


  • To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 17 Nov 2006 10:37:44 +0100
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 17 Nov 2006 01:37:48 -0800
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=b47lIJ9lo1t38tqoOEkaWMxtblJn2+h1WX9JMP4YZ23mOljjA0fA4eQ5so7BtofRGbi5xC6zrUdfJXviEEAJ8DALdz8ObrYwq277aNsVSJSMyd98fPUcMRCb4KdEw35v;
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

Hi Isaku,

Am Donnerstag, 16. November 2006 15:34 schrieb Isaku Yamahata:
> If you have already (even imcomplete) patches, it would be good
> to initiate a discussion with the patch sending a mail of the
> subject [RFC][PATCH] on x86 list.
OK, I will prepare a patch.

>
> > I added a flag is_be to struct arch_domain. Is this ok, or may this
> > produce some problems?
>
> Although I'm not sure how the flag is used, I don't suppose that
> it would cause issues to introduce the new flag.
> I think that big endianess is per-vcpu issue, not per-domain,
My thought was, that the image is completely assembled and linked in big 
endianess. Therewidth it's a property of the domain.

> so that I don't think is_be is necessary. Could you elaborate on is_be?
I must more think on this.. If I better understand the Xen code maybe this 
flag is not needed.
Thanks.

Dietmar.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.