[libvirt test] 157084: regressions - FAIL

2020-11-28 Thread osstest service owner
flight 157084 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/157084/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777 build-amd64-libvirt

[qemu-mainline test] 157076: regressions - FAIL

2020-11-28 Thread osstest service owner
flight 157076 qemu-mainline real [real] flight 157085 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/157076/ http://logs.test-lab.xenproject.org/osstest/logs/157085/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be

[linux-linus test] 157078: regressions - FAIL

2020-11-28 Thread osstest service owner
flight 157078 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/157078/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ws16-amd64 7 xen-install fail REGR. vs. 152332 test-amd64-i386-xl-

[xen-unstable test] 157072: tolerable FAIL

2020-11-28 Thread osstest service owner
flight 157072 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/157072/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-rtds 20 guest-localmigrate/x10 fail pass in 157063 Tests which did not succeed, but

Re: Xen on RP4

2020-11-28 Thread Elliott Mitchell
On Fri, Nov 27, 2020 at 11:59:10PM -0800, Roman Shaposhnik wrote: > On Wed, Nov 25, 2020 at 7:36 PM Elliott Mitchell wrote: > > Well, I've now got everything together for a "proper" Debian Raspberry PI > > installation. Apparently since 5.2 (perhaps earlier, but 5.2 is > > confirmed), Debian's ke

[linux-linus test] 157070: regressions - FAIL

2020-11-28 Thread osstest service owner
flight 157070 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/157070/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ws16-amd64 7 xen-install fail REGR. vs. 152332 test-amd64-i386-xl-

Re: NetBSD dom0 PVH: hardware interrupts stalls

2020-11-28 Thread Manuel Bouyer
On Sat, Nov 28, 2020 at 03:53:11PM +0100, Roger Pau Monné wrote: > > the trace is at > > http://www-soc.lip6.fr/~bouyer/xen-log13.txt > > Thanks! I think I've found the issue and I'm attaching a possible fix > (fix.patch) to this email. In any case I've also attached a further > debug patch, in ca

[qemu-mainline test] 157069: regressions - FAIL

2020-11-28 Thread osstest service owner
flight 157069 qemu-mainline real [real] flight 157074 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/157069/ http://logs.test-lab.xenproject.org/osstest/logs/157074/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be

Re: NetBSD dom0 PVH: hardware interrupts stalls

2020-11-28 Thread Roger Pau Monné
On Fri, Nov 27, 2020 at 10:44:20PM +0100, Manuel Bouyer wrote: > On Fri, Nov 27, 2020 at 09:22:11PM +0100, Roger Pau Monné wrote: > > > > > > But I can confirm that now, entering ^A^A^A gets interrupt going in again > > > > I think there are some weird things with dpci interrupts that I'm > > try

Locate a memory leak in tools modules

2020-11-28 Thread Rroach
Hi, I'm attempting to use address sanitizer in locating bugs in Xen 4-13, while use address sanitizer in tools modules, while I ran some basic instructions like xl, Xen report such bug: = ==2863==ERROR: LeakSanitizer: detected memory

help

2020-11-28 Thread Rroach
Hi, I'm attempting to use address sanitizer in locating bugs in Xen 4-13, while use address sanitizer in tools modules, while I ran some basic instructions like xl, Xen report such bug: = ==2863==ERROR: LeakSanitizer: detected memory

Re: [PATCH RFC 4/6] xen/arm: mm: Allow other mapping size in xen_pt_update_entry()

2020-11-28 Thread Julien Grall
Hi Stefano, On 24/11/2020 00:25, Stefano Stabellini wrote: On Mon, 23 Nov 2020, Julien Grall wrote: Hi Stefano, On 23/11/2020 22:27, Stefano Stabellini wrote: On Fri, 20 Nov 2020, Julien Grall wrote: /* * For arm32, page-tables are different on each CPUs. Yet, they share @@

Re: [PATCH v2] xen/irq: Propagate the error from init_one_desc_irq() in init_*_irq_data()

2020-11-28 Thread Julien Grall
Hi, Please ignore this version as I forgot to call add_maintainers.pl. Sorry for the noise. Cheers, On 28/11/2020 11:31, Julien Grall wrote: From: Julien Grall init_one_desc_irq() can return an error if it is unable to allocate memory. While this is unlikely to happen during boot (called fr

[PATCH v2] xen/irq: Propagate the error from init_one_desc_irq() in init_*_irq_data()

2020-11-28 Thread Julien Grall
From: Julien Grall init_one_desc_irq() can return an error if it is unable to allocate memory. While this is unlikely to happen during boot (called from init_{,local_}irq_data()), it is better to harden the code by propagting the return value. Spotted by coverity. CID: 106529 Signed-off-by: Ju

[PATCH v2] xen/irq: Propagate the error from init_one_desc_irq() in init_*_irq_data()

2020-11-28 Thread Julien Grall
From: Julien Grall init_one_desc_irq() can return an error if it is unable to allocate memory. While this is unlikely to happen during boot (called from init_{,local_}irq_data()), it is better to harden the code by propagting the return value. Spotted by coverity. CID: 106529 Signed-off-by: Ju

Re: [PATCH] xen/irq: Propagate the error from init_one_desc_irq() in init_irq_data()

2020-11-28 Thread Julien Grall
Hi Roger, On 19/11/2020 15:11, Roger Pau Monné wrote: On Thu, Nov 19, 2020 at 02:54:34PM +, Julien Grall wrote: From: Julien Grall init_one_desc_irq() can return an error if it is unable to allocate memory. While this is unlikely to happen during boot (called from init_irq_data()), it is

Re: [PATCH] xen/irq: Propagate the error from init_one_desc_irq() in init_irq_data()

2020-11-28 Thread Julien Grall
On 19/11/2020 23:44, Stefano Stabellini wrote: On Thu, 19 Nov 2020, Julien Grall wrote: From: Julien Grall init_one_desc_irq() can return an error if it is unable to allocate memory. While this is unlikely to happen during boot (called from init_irq_data()), it is better to harden the code

Re: [PATCH] xen/iommu: vtd: Fix undefined behavior pci_vtd_quirks()

2020-11-28 Thread Julien Grall
Hi, On 19/11/2020 14:52, Julien Grall wrote: From: Julien Grall When booting Xen with CONFIG_USBAN=y on Sandy Bridge, UBSAN will throw the following splat: (XEN) (XEN) UBSAN: Undefined behaviour in quirks.c:449:

Re: [PATCH RFC 1/6] xen/arm: mm: Remove special case for CPU0 in dump_hyp_walk()

2020-11-28 Thread Julien Grall
On 19/11/2020 19:07, Julien Grall wrote: From: Stefano Stabellini There is no need to have a special case for CPU0 when converting the page-table virtual address into a physical address. The helper virt_to_maddr() is able to translate any address as long as the root page-tables is mapped in

[xen-unstable test] 157063: tolerable FAIL - PUSHED

2020-11-28 Thread osstest service owner
flight 157063 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/157063/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-ws16-amd64 19 guest-stopfail like 157044 test-amd64-amd64-xl-qemuu-win7-amd64