flight 150900 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150900/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-libvirt-xsm 16 guest-start/debian.repeatfail like 150869
test-amd64-amd64-xl-rtds 18 gues
flight 150905 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150905/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 51ca66c37371b10b378513af126646de22eddb17
baseline version:
xen 1497
flight 150902 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150902/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt broken
test-amd64-amd64-xl-qcow2
On Fri, 5 Jun 2020, 21:43 Marek Marczykowski-Górecki, <
marma...@invisiblethingslab.com> wrote:
> On Fri, Jun 05, 2020 at 06:24:20PM +0100, Paul Durrant wrote:
> > > -Original Message-
> > > From: 'Marek Marczykowski-Górecki'
> > > Sent: 05 June 2020 18:14
> > > To: p...@xen.org
> > > Cc:
From: Julien Grall
xen_pt_next_level() will retrieve the MFN from the entry right after the
page-table has been unmapped.
After calling xen_unmap_table(), there is no guarantee the mapping will
still be valid. Depending on the implementation, this may result to a
data abort in Xen.
Re-order the
flight 150906 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150906/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ws16-amd64 broken in 150901
Tests whic
flight 150908 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150908/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 28dd887d68409c8788c858e29063ee599ebaaa91
baseline version:
ovmf 037d86dd7a9ef36c85bf4
flight 150907 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150907/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 24 guest-migrate/dst_host/src_host/debian.repeat fail
REGR. vs. 150661
Tests w
flight 150909 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150909/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 150694
Tests which did n
flight 150911 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150911/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf cfd73e0065f523e1d56bb32b5c9d48e162c903f8
baseline version:
ovmf 28dd887d68409c8788c85
flight 150910 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150910/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-rtds 18 guest-localmigrate/x10 fail like 150898
test-amd64-amd64-xl-qemut-win7-amd64
Hi xen-devel,
I'm trying to read HVM guest PCI memory from Dom0 using the xenforeignmemory
library, but it's consistently failing with "Invalid Argument", no matter
which PCI device I try.
However, if I try to map in regular (non-device) memory, it seems to work fine.
Do you know why I can't seem
flight 150912 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150912/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-rtds 18 guest-localmigrate/x10 fail like 150661
test-amd64-i386-xl-pvshim12 guest-s
> -Original Message-
> From: Julien Grall
> Sent: 07 June 2020 16:52
> To: xen-devel@lists.xenproject.org
> Cc: p...@xen.org; Julien Grall ; Stefano Stabellini
> ;
> Julien Grall ; Volodymyr Babchuk
> Subject: [PATCH for-4.14] xen/arm: mm: Access a PT entry before the table is
> unmappe
14 matches
Mail list logo
