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] Re: Please pull xen-ia64-unstable

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: Please pull xen-ia64-unstable
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Thu, 22 Sep 2005 12:46:51 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Sep 2005 19:45:34 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcW/rKBJn/D6cXx5QsOrnYnRpboRzwAAGcRw
Thread-topic: [Xen-devel] Re: Please pull xen-ia64-unstable
> > Well, I'm not sure about xen_init() myself. I don't see any 
> > implementation of it for ia64 in your patches -- how does 
> it actually 
> > work?
> 
> Okay, I guess it's just not included in your repo, and is 
> instead part 
> of your xenlinux repo. Fair enough. I don't mind taking this, 
> at least 
> for now.

Correct.  I'm phasing the -sparse checkin (domain0 with no
xen drivers in this phase), but simultaneously
trying to prepare common code for the next phase.
 
> > Also, what about your one-line patch to drivers/acpi/motherboard.c? 
> > That shouldn't be necessary. I'd rather not add it to our 
> sparse tree 
> > if we can avoid it.
> 
> Can I just commit a changeset to delete 
> linux-2.6.-xen-sparse/drivers/acpi/motherboard.c? If so I'll 
> pull your 
> changes and do that.

OK.  FYI, the change in motherboard.c avoids a kernel crash
if the ACPI has a null FADT pointer.  This is technically an
illegal ACPI tree but Xen/ia64 currently creates such a tree.
The right answer is for Xen/ia64 to build a different
fake ACPI tree (with a better fake FADT) but I haven't
gotten around to that yet :-)

Anyway, go ahead and delete that change if you want and I
will handle the problem differently.

Thanks,
Dan

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

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