set_pmd_at() calls native_set_pmd() unconditionally on x86. This was
fine as long as only huge page entries were written via set_pmd_at(),
as Xen pv guests don't support those.
Commit 2c91bd4a4e2e53 ("mm: speed up mremap by 20x on large regions")
introduced a usage of set_pmd_at() possible on pv
flight 133065 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133065/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
flight 133067 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133067/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64
At 04:41 -0700 on 07 Feb (1549514492), Jan Beulich wrote:
> A previously bad situation has become worse with the early setting of
> ->max_vcpus: The value returned by shadow_min_acceptable_pages() has
> further grown, and hence now holds back even more memory from use for
> the p2m.
>
> Make
flight 133060 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133060/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
The pull request you sent on Sat, 9 Feb 2019 15:35:32 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.0-rc6-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3e5e692fcd6ce0d63d8c9bd8677d9aaeec61d70e
Thank you!
--
Deet-doot-dot, I
On 09/02/2019 18:54, Linus Torvalds wrote:
> On Sat, Feb 9, 2019 at 12:24 AM Sander Eikelenboom
> wrote:
>> I haven't got a reproducer so i might be hard to hit it again,
>> system is AMD and this is from the host kernel running under
>> the Xen hypervisor might it matter.
> I think this is a
flight 133052 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133052/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64-xsm
On 09/02/2019 19:51, Sander Eikelenboom wrote:
> On 09/02/2019 19:48, Juergen Gross wrote:
>> On 09/02/2019 19:45, Sander Eikelenboom wrote:
>>> On 09/02/2019 09:26, Sander Eikelenboom wrote:
L.S.,
While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
On Sat, Feb 9, 2019 at 12:24 AM Sander Eikelenboom wrote:
>
> I haven't got a reproducer so i might be hard to hit it again,
> system is AMD and this is from the host kernel running under
> the Xen hypervisor might it matter.
I think this is a Xen bug.
In particular, there's a few poison values
On 09/02/2019 19:48, Juergen Gross wrote:
> On 09/02/2019 19:45, Sander Eikelenboom wrote:
>> On 09/02/2019 09:26, Sander Eikelenboom wrote:
>>> L.S.,
>>>
>>>
>>> While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
>>> additional patches for
>>> already reported other issues i
On 09/02/2019 19:45, Sander Eikelenboom wrote:
> On 09/02/2019 09:26, Sander Eikelenboom wrote:
>> L.S.,
>>
>>
>> While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
>> additional patches for
>> already reported other issues i came across the issue below which i haven't
>>
flight 133073 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133073/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
flight 133037 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133037/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64
Hello,
On Tue, Feb 05, 2019 at 11:44:09AM +, Ian Jackson wrote:
> Jan Beulich writes ("Re: [Xen-devel] preparations for 4.10.3 and 4.9.4"):
> > On 01.02.19 at 12:23, wrote:
> > > For 4.10.3:
> > >
> > > https://lists.xen.org/archives/html/xen-devel/2019-01/msg01451.html
> >
> > Ian, this
On 08.02.19 20:21, Amit Tomer wrote:
Hi,
Hi
Would try changes mentioned by you.
We managed to boot XEN with dom0 kernel on H3.
That's great.
But we see following , when we try to domU guest:
# xl create -c config.xl
Parsing config from config.xl
libxl: error:
Hello,
Hans van Kranenburg, le sam. 09 févr. 2019 17:01:55 +0100, a ecrit:
> > I have forwarded the original mail: all VM I/O get stuck, and thus the
> > VM becomes unusable.
>
> These are in many cases the symptoms of running out of "grant frames".
Oh! That could be it indeed. I'm wondering
Hi,
On 2/9/19 12:16 AM, Samuel Thibault wrote:
>
> Hans van Kranenburg, le ven. 08 févr. 2019 20:18:44 +0100, a ecrit:
>> [...]
>>
>> On 2/8/19 6:13 PM, Samuel Thibault wrote:
>>>
>>> Sacha, le ven. 08 févr. 2019 18:00:22 +0100, a ecrit:
On Debian GNU/Linux 9.7 (stretch) amd64, we have a
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.0-rc6-tag
xen: fixes for 5.0-rc6
It contains two very minor fixes: one remove of a #include for an unused
header and a fix of the xen ML address in MAINTAINERS.
Thanks.
Juergen
flight 133056 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133056/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
flight 133038 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133038/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd 50ac923f6c318317731e58c26ff02a7608f8a056
baseline version:
freebsd
flight 133034 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133034/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64
L.S.,
While testing a Linux 5.0-rc5-ish kernel (pull of yesterday) with some
additional patches for
already reported other issues i came across the issue below which i haven't
seen with 4.20.x
I haven't got a reproducer so i might be hard to hit it again,
system is AMD and this is from the
23 matches
Mail list logo
