From: Juergen Gross <jgross@suse.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [linux-linus bisection] complete test-amd64-amd64-xl-pvhv2-amd
Date: Thu, 5 Apr 2018 09:11:44 +0200 [thread overview]
Message-ID: <259430ee-7404-7d3d-0b64-4c341edcb56c@suse.com> (raw)
In-Reply-To: <d3c1bca6-57c7-2225-f2fc-aa1153687bb1@eikelenboom.it>
On 03/04/18 18:55, Sander Eikelenboom wrote:
> On 03/04/18 12:29, Juergen Gross wrote:
>> On 03/04/18 12:19, osstest service owner wrote:
>>> branch xen-unstable
>>> xenbranch xen-unstable
>>> job test-amd64-amd64-xl-pvhv2-amd
>>> testid guest-start
>>>
>>> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.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: 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: 4a5733771e6f33918eba07b584cccce564a67ac1
>>> Bug not present: 1c2e0f9e4f263714db917eb54f8d1c2d1463ed4c
>>> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/118498/
>>>
>>>
>>> commit 4a5733771e6f33918eba07b584cccce564a67ac1
>>> Author: Juergen Gross <jgross@suse.com>
>>> Date: Fri Dec 1 15:14:07 2017 +0100
>>>
>>> libxl: put RSDP for PVH guest near 4GB
>>>
>>> Instead of locating the RSDP table below 1MB put it just below 4GB
>>> like the rest of the ACPI tables in case of PVH guests. This will
>>> avoid punching more holes than necessary into the memory map.
>>>
>>> Signed-off-by: Juergen Gross <jgross@suse.com>
>>> Acked-by: Wei Liu <wei.liu2@citrix.com>
>>> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
>>
>> The corresponding Linux kernel patch just made it upstream.
>>
>>
>> Juergen
>
> Hi Juergen,
>
> Are those kernel patches heading for linux-stable as well ?
Greg refuses to take them, sorry.
> I ask this, because it would be nice to be able to use PVH on Xen 4.11 release with a distro kernel
> (4.9 or 4.14 stable for instance for Debian).
I think you have to request the distributor to take them (I'll add them
to the SUSE kernel for SLE15 / openSUSE 15).
> PVH worked fine with xen-4.11-to-be up until this commit, so the kernel patches fix this (non-kernel) regression.
It _is_ a kernel regression, as the kernel wasn't using the PVH
interface correctly.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-05 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 10:19 [linux-linus bisection] complete test-amd64-amd64-xl-pvhv2-amd osstest service owner
2018-04-03 10:29 ` Juergen Gross
2018-04-03 16:55 ` Sander Eikelenboom
2018-04-04 6:37 ` Juergen Gross
2018-04-05 7:11 ` Juergen Gross [this message]
2018-04-05 7:37 ` Sander Eikelenboom
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 6:20 osstest service owner
2018-01-31 21:13 osstest service owner
2017-11-22 21:57 osstest service owner
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=259430ee-7404-7d3d-0b64-4c341edcb56c@suse.com \
--to=jgross@suse.com \
--cc=linux@eikelenboom.it \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.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 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).