xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jean Guyader <jean.guyader@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jean Guyader <jean.guyader@eu.citrix.com>
Subject: Re: [xen-unstable bisection] complete test-amd64-i386-rhel6hvm-intel
Date: Mon, 21 Nov 2011 21:32:51 +0000	[thread overview]
Message-ID: <CAF07403.2553D%keir.xen@gmail.com> (raw)
In-Reply-To: <CAEBdQ90hBQOzVoQXH6Lg1omkTs=JRUM=Qz4_6u09D-Pa=DAQAA@mail.gmail.com>

On 21/11/2011 19:43, "Jean Guyader" <jean.guyader@gmail.com> wrote:

> On 21 November 2011 18:47, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 21/11/2011 11:55, "Keir Fraser" <keir.xen@gmail.com> wrote:
>> 
>>> On 21/11/2011 11:37, "Ian Jackson" <Ian.Jackson@eu.citrix.com> 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.

 -- Keir

> Jean
> 
>>>  -- Keir
>>> 
>>>>>   changeset:   24163:7a9a1261a6b0
>>>>>   user:        Jean Guyader <jean.guyader@eu.citrix.com>
>>>>>   date:        Fri Nov 18 13:41:33 2011 +0000
>>>>> 
>>>>>       add_to_physmap: Move the code for XENMEM_add_to_physmap
>>>>> 
>>>>>       Move the code for the XENMEM_add_to_physmap case into it's own
>>>>>       function (xenmem_add_to_physmap).
>>>>> 
>>>>>       Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com>
>>>>>       Committed-by: Keir Fraser <keir@xen.org>
>>>> 
>>>> Ian.
>>> 
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>> 

  reply	other threads:[~2011-11-21 21:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  3:40 [xen-unstable bisection] complete test-amd64-i386-rhel6hvm-intel xen.org
2011-11-21 11:37 ` Ian Jackson
2011-11-21 11:55   ` Keir Fraser
2011-11-21 18:47     ` Keir Fraser
2011-11-21 19:43       ` Jean Guyader
2011-11-21 21:32         ` Keir Fraser [this message]
2011-11-21 21:51           ` Jean Guyader
  -- strict thread matches above, loose matches on Subject: below --
2013-07-21  3:26 xen.org
2013-07-21  5:30 ` Ian Campbell
2013-07-21 15:15   ` Ian Campbell
2013-02-06  7:04 xen.org
2012-02-25 16:48 xen.org
2011-09-01 15:54 xen.org
2011-09-01 16:26 ` Ian Jackson
2011-09-01 17:22   ` Laszlo Ersek
2011-09-02  7:11     ` Ian Campbell
2011-09-01 17:48   ` Laszlo Ersek
2011-09-01 19:28   ` Andrew Jones
2011-09-02 11:08     ` Ian Jackson
2011-07-07 14:41 xen.org
2010-12-22  2:12 xen.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF07403.2553D%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jean.guyader@eu.citrix.com \
    --cc=jean.guyader@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).