flight 154844 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154844/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-prev
branch xen-4.14-testing
xenbranch xen-4.14-testing
job test-xtf-amd64-amd64-2
testid xtf/test-hvm64-xsa-221
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenb
branch xen-4.14-testing
xenbranch xen-4.14-testing
job test-xtf-amd64-amd64-1
testid xtf/test-pv64-xsa-221
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbi
branch xen-4.14-testing
xenbranch xen-4.14-testing
job test-xtf-amd64-amd64-2
testid xtf/test-pv64-xsa-221
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbi
flight 154740 xen-4.11-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154740/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 debian-hvm-install fail
REGR. vs. 15171
flight 154753 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154753/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 broken
test-amd64-i386-xl-qe
On Fri, Sep 25, 2020 at 09:54:52AM -0400, Qian Cai wrote:
> On Wed, 2020-08-26 at 13:17 +0200, Thomas Gleixner wrote:
> > From: Thomas Gleixner
> >
> > The arch_.*_msi_irq[s] fallbacks are compiled in whether an architecture
> > requires them or not. Architectures which are fully utilizing hierar
Hi Andrew,
On 22/09/2020 19:56, Andrew Cooper wrote:
On 22/09/2020 19:20, Julien Grall wrote:
+
#endif /* __ASM_DOMAIN_H__ */
/*
diff --git a/xen/include/public/domctl.h b/xen/include/public/domctl.h
index 5c5e55ebcb76..7564df5e8374 100644
--- a/xen/include/public/domctl.h
+++ b/xen/inc
Hi,
On 24/09/2020 19:02, Oleksandr wrote:
On 24.09.20 19:02, Oleksandr wrote:
On 24.09.20 14:08, Jan Beulich wrote:
On 23.09.2020 22:16, Oleksandr wrote:
On 23.09.20 21:03, Julien Grall wrote:
On 10/09/2020 21:22, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
@@ -91,6 +108,28 @@ s
On 26.09.20 16:12, Julien Grall wrote:
Hi,
Hi Julien.
On 24/09/2020 19:02, Oleksandr wrote:
On 24.09.20 19:02, Oleksandr wrote:
On 24.09.20 14:08, Jan Beulich wrote:
On 23.09.2020 22:16, Oleksandr wrote:
On 23.09.20 21:03, Julien Grall wrote:
On 10/09/2020 21:22, Oleksandr Tyshchenko
Hi Oleksandr,
On 24/09/2020 19:22, Oleksandr wrote:
On 24.09.20 20:25, Julien Grall wrote:
On 23/09/2020 21:16, Oleksandr wrote:
On 23.09.20 21:03, Julien Grall wrote:
On 10/09/2020 21:22, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Could you please clarify how this patch could
(+ Paul and Andre)
Hi,
Adding Paul as the author of DMOP and Andre as this is GIC related.
On 10/09/2020 21:22, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Looking at the PoC I shared with you, this code was originally written
by me.
This patch adds ability to the device emu
On 26.09.20 16:50, Julien Grall wrote:
(+ Paul and Andre)
Hi,
Hi Julien
Adding Paul as the author of DMOP and Andre as this is GIC related.
On 10/09/2020 21:22, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Looking at the PoC I shared with you, this code was originally wri
On 26.09.20 16:21, Julien Grall wrote:
Hi Oleksandr,
Hi Julien.
On 24/09/2020 19:22, Oleksandr wrote:
On 24.09.20 20:25, Julien Grall wrote:
On 23/09/2020 21:16, Oleksandr wrote:
On 23.09.20 21:03, Julien Grall wrote:
On 10/09/2020 21:22, Oleksandr Tyshchenko wrote:
From: Oleksandr T
flight 154771 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154771/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt broken
build-i386-libvirt4 host-install(4
flight 154876 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154876/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-prev
flight 154758 xen-4.12-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154758/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm broken
test-amd64-i386-freebsd10-amd64
From: Julien Grall
Commit 022387ee1ad3 "xen/arm: mm: Don't open-code Xen PT update in
{set, clear}_fixmap()" enforced that each set_fixmap() should be
paired with a clear_fixmap(). Any failure to follow the model would
result to a platform crash.
Unfortunately, the use of fixmap in the ACPI code
From: Julien Grall
Hi all,
Xen on ARM has been broken for quite a while on ACPI systems. This
series aims to fix it.
Unfortunately I don't have a system with ACPI v6.0 or later (QEMU seems
to only support 5.1). So I did only some light testing.
I have only build tested the x86 side so far.
Ch
From: Julien Grall
The functions acpi_os_{un,}map_memory() are meant to be arch-agnostic
while the __acpi_os_{un,}map_memory() are meant to be arch-specific.
Currently, the former are still containing x86 specific code.
To avoid this rather strange split, the generic helpers are reworked so
the
From: Julien Grall
Since commit 6e3e77120378 "xen/arm: setup: Relocate the Device-Tree
later on in the boot", the device-tree will not be kept mapped when
using ACPI.
However, a few places are calling dt_unreserved_regions() which expects
a valid DT. This will lead to a crash.
As the DT should
From: Julien Grall
Dom0less requires a device-tree. However, since commit 6e3e77120378
"xen/arm: setup: Relocate the Device-Tree later on in the boot", the
device-tree will not get unflatten when using ACPI.
This will lead to a crash during boot.
Given the complexity to setup dom0less with ACPI
On Sat, Sep 26, 2020 at 09:55:38PM +0100, Julien Grall wrote:
> Xen on ARM has been broken for quite a while on ACPI systems. This
> series aims to fix it.
>
> Unfortunately I don't have a system with ACPI v6.0 or later (QEMU seems
> to only support 5.1). So I did only some light testing.
>
> I h
flight 154913 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154913/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-prev
flight 154909 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/154909/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-pvops
branch xen-4.13-testing
xenbranch xen-4.13-testing
job test-xtf-amd64-amd64-4
testid xtf/test-pv64-xsa-221
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbi
26 matches
Mail list logo
