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/
Home Products Support Community News


Re: [Xen-devel] [xen-4.0-testing test] 2061: regressions - FAIL

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [xen-4.0-testing test] 2061: regressions - FAIL
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Fri, 3 Sep 2010 11:04:28 -0700
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 03 Sep 2010 11:05:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19585.13976.404518.700860@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
Mail-followup-to: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
References: <E1OrNWT-0006tR-VX@xxxxxxxxxxxxxxxxxxx> <19585.11453.829459.233212@xxxxxxxxxxxxxxxxxxxxxxxx> <20100903171729.GA16367@xxxxxxxxxxxxxxxxx> <19585.11893.756884.189394@xxxxxxxxxxxxxxxxxxxxxxxx> <20100903173803.GA17663@xxxxxxxxxxxxxxxxx> <19585.13107.325426.697689@xxxxxxxxxxxxxxxxxxxxxxxx> <20100903175413.GB17663@xxxxxxxxxxxxxxxxx> <19585.13976.404518.700860@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2010-08-04)
On Friday, 03 September 2010 at 18:55, Ian Jackson wrote:
> Brendan Cully writes ("Re: [Xen-devel] [xen-4.0-testing test] 2061: 
> regressions - FAIL"):
> > Until the kernel modules are in their proper place, I think a less
> > drastic fix for your test suites would be to edit
> > tools/remus/kmod/Makefile and change
> > 
> > test -d $(KERNELDIR)
> > 
> > to
> > 
> > test -f $(KERNELDIR)/Module.symvers
> > 
> > which will still silently fail to build the modules if tools/remus
> > builds too early, but should suppress failure warnings. Completely
> > untested.
> I don't think this is reliable, is it ?  As that .symvers file can be
> created before the kernel build is complete.  So we can still reenter
> the whole kernel build.

What do you mean 'reenter the whole kernel build'? Are you under the
impression that the kmod tree is somehow actually building in the
kernel build directory?

As I said in an earlier email, it doesn't do that. It is just using
the kernel header files, like any other third party module. Normally
you could find them under /lib/modules/foo/build, but obviously that
doesn't apply here.

Xen-devel mailing list