All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xen.org
Subject: Re: [linux-3.10 bisection] complete test-amd64-i386-rumpuserxen-i386
Date: Tue, 15 Dec 2015 10:42:58 +0100	[thread overview]
Message-ID: <566FE0A2.2050308@suse.com> (raw)
In-Reply-To: <566FC84F.5070105@suse.com>

On 15/12/15 08:59, Juergen Gross wrote:
> On 15/12/15 08:24, osstest service owner wrote:
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-i386-rumpuserxen-i386
>> testid guest-start
>>
>> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
>> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
>> Tree: rumpuserxen git://xenbits.xen.org/rumpuser-xen.git
>> Tree: rumpuserxen_buildrumpsh https://github.com/rumpkernel/buildrump.sh.git
>> Tree: rumpuserxen_netbsdsrc https://github.com/rumpkernel/src-netbsd
>> Tree: xen git://xenbits.xen.org/xen.git
>>
>> *** Found and reproduced problem changeset ***
>>
>>   Bug is in tree:  xen git://xenbits.xen.org/xen.git
>>   Bug introduced:  81a76e4b12961a9f54f5021809074196dfe6dbba
>>   Bug not present: cd353959cdfbe06c2a6abfd73f03f40b84e1e3f1
>>   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/66373/
>>
>>
>>   commit 81a76e4b12961a9f54f5021809074196dfe6dbba
>>   Author: Juergen Gross <jgross@suse.com>
>>   Date:   Thu Nov 12 14:43:35 2015 +0100
>>   
>>       libxc: rework of domain builder's page table handler
>>       
>>       In order to prepare a p2m list outside of the initial kernel mapping
>>       do a rework of the domain builder's page table handler. The goal is
>>       to be able to use common helpers for page table allocation and setup
>>       for initial kernel page tables and page tables mapping the p2m list.
>>       This is achieved by supporting multiple mapping areas. The mapped
>>       virtual addresses of the single areas must not overlap, while the
>>       page tables of a new area added might already be partially present.
>>       Especially the top level page table is existing only once, of course.
>>       
>>       Currently restrict the number of mappings to 1 because the only mapping
>>       now is the initial mapping created by toolstack. There should not be
>>       behaviour change and guest visible change introduced.
>>       
>>       Signed-off-by: Juergen Gross <jgross@suse.com>
>>       Reviewed-by: Wei Liu <wei.liu2@citrix.com>
> 
> Hmm, reminds me of the problem which should have been corrected with
> commit 43e99d38cd9253267982f5c29205f2d273f7d65e. Is there a log
> somewhere with this commit included?

Oops, commit is off by one. It should be:
c8eb0ec277ae387e78d685523e0fee633e46f046

Juergen

  reply	other threads:[~2015-12-15  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15  7:24 [linux-3.10 bisection] complete test-amd64-i386-rumpuserxen-i386 osstest service owner
2015-12-15  7:59 ` Juergen Gross
2015-12-15  9:42   ` Juergen Gross [this message]
2015-12-15  9:43   ` Ian Campbell

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=566FE0A2.2050308@suse.com \
    --to=jgross@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.