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

[Xen-devel] Re: [patch] [ppc] use xen_ulong_t in start_info

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [patch] [ppc] use xen_ulong_t in start_info
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Fri, 28 Jul 2006 17:34:49 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 28 Jul 2006 15:34:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <37ac78ac9b6c6d1b960163913d9cf9a8@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <1154032824.3128.22.camel@xxxxxxxxxxxxxxxxxxxxx> <37ac78ac9b6c6d1b960163913d9cf9a8@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2006-07-28 at 10:57 +0100, Keir Fraser wrote:
> On 27 Jul 2006, at 21:40, Hollis Blanchard wrote:
> 
> > Keir, you mentioned that start_info probably doesn't make much sense 
> > for
> > PowerPC. However, if for no other reason than linux/drivers/xen has 
> > many
> > references to it, we'd like to fix it for now and figure out how to
> > replace it later.
> 
> I think that structure is quite x86-specific. I'd be happy to see 
> direct references to start_info replaced in drivers/xen. Obvious (and 
> ugly) low-hanging fruit is test for SIF_INITDOMAIN. Replacing with 
> arch-specific is_initial_domain() or similar would be a great patch to 
> receive.

OK.

> A couple of the others (e.g., console_mfn, store_mfn) are a 
> bit harder -- how do you communicate those on ppc?

We intend to communicate those via the Open Firmware device tree.
(There's a brief overview at
http://wiki.xensource.com/xenwiki/XenPPC/OpenFirmware .)

-- 
Hollis Blanchard
IBM Linux Technology Center


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

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