From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [xen-unstable bisection] complete test-amd64-i386-rhel6hvm-intel Date: Mon, 21 Nov 2011 21:32:51 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jean Guyader Cc: "xen-devel@lists.xensource.com" , Ian Jackson , Jean Guyader List-Id: xen-devel@lists.xenproject.org On 21/11/2011 19:43, "Jean Guyader" wrote: > On 21 November 2011 18:47, Keir Fraser wrote: >> On 21/11/2011 11:55, "Keir Fraser" wrote: >> = >>> On 21/11/2011 11:37, "Ian Jackson" 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 *** >>>>> = >>>>> =A0 Bug is in tree: =A0xen http://xenbits.xen.org/staging/xen-unstabl= e.hg >>>>> =A0 Bug introduced: =A07a9a1261a6b0 >>>>> =A0 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=3D=3D0. I checked in a reworked version that is closer t= o the original code. = Hopefully our tests will work again now. -- Keir > Jean > = >>> =A0-- Keir >>> = >>>>> =A0 changeset: =A0 24163:7a9a1261a6b0 >>>>> =A0 user: =A0 =A0 =A0 =A0Jean Guyader >>>>> =A0 date: =A0 =A0 =A0 =A0Fri Nov 18 13:41:33 2011 +0000 >>>>> = >>>>> =A0 =A0 =A0 add_to_physmap: Move the code for XENMEM_add_to_physmap >>>>> = >>>>> =A0 =A0 =A0 Move the code for the XENMEM_add_to_physmap case into it'= s own >>>>> =A0 =A0 =A0 function (xenmem_add_to_physmap). >>>>> = >>>>> =A0 =A0 =A0 Signed-off-by: Jean Guyader >>>>> =A0 =A0 =A0 Committed-by: Keir Fraser >>>> = >>>> Ian. >>> = >>> = >> = >> = >> = >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> =