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: linux-next: Tree for July 25 (xen)

To: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: linux-next: Tree for July 25 (xen)
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 4 Aug 2011 18:30:18 -0400
Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, linux-next@xxxxxxxxxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>
Delivery-date: Thu, 04 Aug 2011 15:31:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110804131516.c4da6595.rdunlap@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/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: <20110725162542.39ea8d8cbd51604523635c1a@xxxxxxxxxxxxxxxx> <20110725144629.b752bf14.rdunlap@xxxxxxxxxxxx> <20110804193534.GB12729@xxxxxxx> <20110804195539.GA11198@xxxxxxxxxxxx> <20110804131516.c4da6595.rdunlap@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
> > >  arch/x86/xen/trace.c:44:2: error: array index in initializer not of 
> > > integer type
> > >  arch/x86/xen/trace.c:44:2: error: (near initialization for 
> > > ‘xen_hypercall_names’)
> > >  arch/x86/xen/trace.c:45:1: error: ‘__HYPERVISOR_arch_4’ undeclared here 
> > > (not in a function)
> > >  arch/x86/xen/trace.c:45:2: error: array index in initializer not of 
> > > integer type
> > >  arch/x86/xen/trace.c:45:2: error: (near initialization for 
> > > ‘xen_hypercall_names’)
> > 
> > Oh, that I haven't seen. Can you send me the .config for that please.
> 
> You can't be trying very hard then.  I see lots of these (but no,

Hm, It is not obvious to me what is causing that compile failure. Any ideas?

> I haven't reported them.  One can grow weary of reporting xen bugs.)
> 
> 
> > > even after:
> > > 
> > >  b3c4b9825075: xen/tracing: fix compile errors when tracing is disabled.
> > > 
> > > Btw., that the heck is going on with the commit that introduced the 
> > > build failure:
> > > 
> > >  commit bd9ddc875b6659f9f74dcfd285c472bc58041abd
> > >  Author:     Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
> > >  AuthorDate: Mon Jun 20 17:52:13 2011 -0700
> > >  Commit:     Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
> > >  CommitDate: Mon Jul 18 15:43:46 2011 -0700
> > > 
> > > It was apparently rebased shortly before the merge window and sent to 
> > 
> > Well, the rebase I get - it was done on top of the merge that introduced
> > the new functionality.
> > 
> > > Linus 3 days later, with little to no linux-next testing ...
> > 
> > <Hmm> It did fix the compile problem.. albeit it created another one.
> > > 
> > > I'm absolutely unhappy about how the Xen tree is being run. It's 
> > > using a sloppy, crappy workflow and it is producing crap.
> > 
> > Do you have a manual of how you guys run your workflow?
> 
> I just run 30-50 randconfigs per night (cron job).

Ok, do you have an mailing list where you send the output too?

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