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] recent major -unstable changes cause ia64 build to be br

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] recent major -unstable changes cause ia64 build to be broken
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Tue, 10 May 2005 16:08:54 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 10 May 2005 23:33:37 +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: AcVVnbAyzod8pwSRQFCfvZHVBGqrYwAF1GDw
Thread-topic: [Xen-devel] recent major -unstable changes cause ia64 build to be broken
Keir --

Thanks for putting those changes in.  I have already
grabbed and tested them with latest ia64 bits.

Please pull:
bk://xen-ia64.bkbits.net/xeno-unstable-ia64.bk

and life should be happy again for ia64 users :-)

Thanks,
Dan 

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
> Sent: Tuesday, May 10, 2005 2:17 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel
> Subject: Re: [Xen-devel] recent major -unstable changes cause 
> ia64 build to be broken
> 
> 
> On 10 May 2005, at 20:16, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > It looks like the recent changes to update
> > to base off of 2.6.11 rather than 2.4 has badly
> > broken the ia64 build.  I'm still looking to figure
> > out exactly what is wrong but it doesn't look easy.
> 
> The most pertinent changes are:
>   1. Upgrade ACPI common code from Linux 2.6.11
>   2. Remove PCI code
> 
> There are a few others (e.g., starting slowly to move to Linux's 
> cpumask_t), but I think they are unlikely to be difficult to fix for. 
> Certainly they have resulted in very few changes to files in 
> include/xen.
> 
> Change (1) ought not to be too difficult to fix for ia64 as most of 
> your code is 2.6-based already. I just pulled the 2.6.11 x86-specific 
> acpi source files into Xen and tweaked them a very small 
> amount to get 
> them to build.
> 
> Change (2) is also likely very easy, since you say you leave most 
> hardware setup to domain0 anyway. I doubt you need to do PCI 
> enumeration or scanning in Xen itself? Culling you in-Xen PCI code 
> entirely is probably the best way forward.
> 
>   -- Keir
> 
> 

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

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