flight 134772 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134772/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
flight 134738 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134738/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 7 xen-boot fail REGR. vs. 134640
build-i386-libvirt
flight 134775 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134775/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
coverity-amd647 coverity-upload fail REGR. vs. 133615
version t
flight 134658 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134658/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken in 134507
build-arm64
flight 134778 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134778/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
At the moment, we hide PMU's from domain 0 and XEN boot fails on platform[1]
where DTS contains "arm,cortex-a53-pmu" as compatible string for PMU node.
This patch simply adds "arm,cortex-a53-pmu" to list of blacklisted PMUs.
[1]:
https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/
Hi,
On 4/14/19 3:33 PM, Amit Singh Tomar wrote:
At the moment, we hide PMU's from domain 0 and XEN boot fails on platform[1]
where DTS contains "arm,cortex-a53-pmu" as compatible string for PMU node.
"Domain 0 and Xen boot fails" is pretty vague. How does it fail?
In general, a commit message
Hi Amit,
On 4/14/19 7:33 AM, Amit Singh Tomar wrote:
This patch adds earlyprintk support for Amlogic Meson SoC based
boards.
It relies on firmware[1] to initialize the UART.
Do all the firmware existing for this platform initialize the UART?
Cheers,
--
Julien Grall
flight 134677 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134677/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken in 134576
build-arm64
Hi,
On 4/12/19 12:16 PM, Jan Beulich wrote:
On 11.04.19 at 15:25, wrote:
The use of return_reg() assumes ARM's 32bit ABI. Therefore, a failure such as
-EINVAL will appear as a large positive number near 4 billion to a 64bit ARM
guest which happens to use continue_hypercall_on_cpu().
Introduc
Hi,
On 4/9/19 1:21 PM, Jan Beulich wrote:
On 09.04.19 at 11:50, wrote:
On 08/04/2019 15:29, Jan Beulich wrote:
On 08.04.19 at 13:47, wrote:
de-allocation step aside, I am not really convinced you can reuse
guest_remove_page() here. On x86, the function will not work on certain
p2m types. Is
Hello,
> Do all the firmware existing for this platform initialize the UART?
U-boot does also initialize the uart for this platform.
https://github.com/u-boot/u-boot/blob/master/drivers/serial/serial_meson.c#L44
Thanks,
-Amit
___
Xen-devel mailing lis
On 4/14/19 5:35 PM, Amit Tomer wrote:
Hello,
Hi,
Do all the firmware existing for this platform initialize the UART?
U-boot does also initialize the uart for this platform.
https://github.com/u-boot/u-boot/blob/master/drivers/serial/serial_meson.c#L44
How about replacing "It relies on f
Hi Oleksandr,
On 4/8/19 11:14 AM, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Extend driver to be able to handle other SCIF(X) compatible
interfaces as well. These interfaces have lot in common,
but mostly differ in offsets and bits for some registers.
Can you briefly explain in t
Hi Olekansdr,
On 4/8/19 11:14 AM, Oleksandr Tyshchenko wrote:
diff --git a/xen/drivers/char/scif-uart.c b/xen/drivers/char/scif-uart.c
index 958f717..94cb230 100644
--- a/xen/drivers/char/scif-uart.c
+++ b/xen/drivers/char/scif-uart.c
@@ -1,7 +1,7 @@
/*
* xen/drivers/char/scif-uart.c
*
-
flight 134782 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134782/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
Hi,
On 4/8/19 11:14 AM, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Extend early prink code to be able to handle other SCIF(X)
compatible interfaces as well. These interfaces have lot in common,
but mostly differ in offsets and bits for some registers.
Introduce "EARLY_PRINTK_VERSI
This patch adds earlyprintk support for Amlogic Meson SoC based
boards.
ATF[1] and U-boot[2] already initialize the UART for us. So no need to do it
again.
Tested With:
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_K2
[1]:
https://github.com/ARM-software/arm-trusted-firmware/blob/master/d
Hi Oleksandr,
On 4/8/19 11:14 AM, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
This patch makes possible to use existing early prink code
for Renesas "Stout" board based on R-Car H2 SoC (SCIFA).
The "EARLY_PRINTK_VERSION" for that board should be 'A':
CONFIG_EARLY_PRINTK=scif,0xe6c4
flight 134786 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134786/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
flight 134678 qemu-upstream-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134678/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 broken in 134580
build-arm64-xsm
flight 134685 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134685/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 133846
Tests which did not suc
flight 134789 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134789/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
flight 134796 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134796/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-debianhvm-amd64
testid guest-saverestore
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qe
On Fri, Apr 12, 2019 at 1:50 PM Tamas K Lengyel wrote:
>
> The page_lock system was not intended to be used outside the PV pagetable
> code. Replace its use in mem_sharing with an internal rwlock.
>
After further testing I'm actually running into a lot of strange
problems with this when domains w
flight 134776 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134776/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 6 kernel-build fail REGR. vs. 134640
build-i386
flight 134800 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134800/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 133991
Tests which
This email only tracks big items for xen.git tree. Please reply for items you
would like to see in 4.13 so that people have an idea what is going on and
prioritise accordingly.
You're welcome to provide description and use cases of the feature you're
working on.
= Timeline =
We now adopt a fixed
29 matches
Mail list logo
