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: SOLVED: Re: [Xen-devel] Issue with pv_ops Kernel 2.6.31.6 and Xen [y

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: SOLVED: Re: [Xen-devel] Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@xxxxxxxxxx: [PATCH 01/35] x86: fix sci on ioapic 1]
From: M A Young <m.a.young@xxxxxxxxxxxx>
Date: Wed, 17 Feb 2010 11:56:25 +0000 (GMT)
Cc: Marcial Rion <marcial.rion@xxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 17 Feb 2010 03:57:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100217083354.GT2861@xxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100210153954.GA9539@xxxxxxxxxxxxxxxxxxx> <4B7731DE.8020905@xxxxxxxxxxxxxx> <20100216181005.GC21067@xxxxxxxxxxxxxxxxxxx> <4B7B1349.9020003@xxxxxxxx> <20100217083354.GT2861@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (GSO 1167 2008-08-23)
On Wed, 17 Feb 2010, Pasi Kärkkäinen wrote:

On Tue, Feb 16, 2010 at 01:51:05PM -0800, Jeremy Fitzhardinge wrote:
Yes.  At the moment xen/next is based on plain 2.6.32 because that is
also an ancestor version of mainline git development.  Once the 2.6.32
tree basically works (which should be close), then I can merge all the
stable branch changes onto it and call it "xen/stable" or something.


So that means I should try xen/next now? :)

I wouldn't recommend it yet. I have been trying it, but I haven't yet got it to boot, and my most recent attempt a couple of days ago didn't even build (the errors were

drivers/xen/xenbus/xenbus_probe.c: In function 'exists_connecting_device':
drivers/xen/xenbus/xenbus_probe.c:791: error: 'xenbus_frontend' undeclared (first use in this function) drivers/xen/xenbus/xenbus_probe.c:791: error: (Each undeclared identifier is reported only once drivers/xen/xenbus/xenbus_probe.c:791: error: for each function it appears in.)
drivers/xen/xenbus/xenbus_probe.c: In function 'wait_for_devices':
drivers/xen/xenbus/xenbus_probe.c:863: error: 'xenbus_frontend' undeclared (first use in this function)
make[3]: *** [drivers/xen/xenbus/xenbus_probe.o] Error 1

        Michael Young
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>