Re: [Xen-devel] [xen-unstable bisection] complete test-amd64-i386-rhel6hvm-intel

[Jean Guyader <jean.guyader@xxxxxxxxxxxxx>]

On 21/11 09:32, Keir Fraser wrote:
> On 21/11/2011 19:43, "Jean Guyader" <jean.guyader@xxxxxxxxx> wrote:
> 
> > On 21 November 2011 18:47, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> >> On 21/11/2011 11:55, "Keir Fraser" <keir.xen@xxxxxxxxx> wrote:
> >> 
> >>> On 21/11/2011 11:37, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> >>> 
> >>>> xen.org writes ("[xen-unstable bisection] complete
> >>>> test-amd64-i386-rhel6hvm-intel"):
> >>>>> branch xen-unstable
> >>>>> xen branch xen-unstable
> >>>>> job test-amd64-i386-rhel6hvm-intel
> >>>>> test redhat-install
> >>>>> 
> >>>>> Tree: linux git://github.com/jsgf/linux-xen.git
> >>>>> Tree: qemu git://hg.uk.xensource.com/HG/qemu-xen-unstable.git
> >>>>> Tree: xen http://xenbits.xen.org/staging/xen-unstable.hg
> >>>>> 
> >>>>> *** Found and reproduced problem changeset ***
> >>>>> 
> >>>>> ? Bug is in tree: ?xen http://xenbits.xen.org/staging/xen-unstable.hg
> >>>>> ? Bug introduced: ?7a9a1261a6b0
> >>>>> ? Bug not present: 9a1a71f7bef2
> >>>> 
> >>>> This seems to have completely broken HVM ...
> >>> 
> >>> I'll revert if there's no fix forthcoming.
> >> 
> >> I hear silence so I will revert the series tomorrow morning.
> >> 
> > 
> > Ok. I didn't managed to replicate the issue yet.
> 
> Actually, it wasn't too hard to work out. This bisection is misleading
> though, as it's zeroed in on the RCU locking bug, which is already fixed.
> The bug is actually in a later changeset which modifies hvmloader.
> 
> Looking at the hvmloader/pci.c changes, the unconditional assignment to
> low_mem_pgend after the loop is obviously wrong. As is removing the handling
> for high_mem_pgend==0. I checked in a reworked version that is closer to the
> original code. 
> 
> Hopefully our tests will work again now.
> 

Thanks for looking into it. I would like this serie to get applied in 4.1
but I think that the code have changed a bit. I'll send a version for 4.1
similar to the one we have in xen-unstable.

Jean

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