[Xen-devel] [libvirt test] 144633: regressions - FAIL

2019-12-08 Thread osstest service owner
flight 144633 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/144633/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 144517 build-i386-libvirt

[Xen-devel] [xen-unstable test] 144631: tolerable FAIL

2019-12-08 Thread osstest service owner
flight 144631 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/144631/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-rtds 16 guest-localmigrate fail in 144619 pass in 144631 test-armhf-armhf-xl-rtds 12

[Xen-devel] [xen-unstable-coverity test] 144634: all pass - PUSHED

2019-12-08 Thread osstest service owner
flight 144634 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/144634/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen ae25407faaaddf4abe44137ebf0e177a8c8f9858 baseline version: xen d7c3

[Xen-devel] [PATCH] Remove myself as vm_event maintainer

2019-12-08 Thread Razvan Cojocaru
--- MAINTAINERS | 1 - 1 file changed, 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 9c827ad759..012c847ebd 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -428,7 +428,6 @@ L: xen-devel@lists.xenproject.org F: unmodified_drivers/linux-2.6/ VM EVENT, MEM ACCESS and MONITOR -M:

Re: [Xen-devel] [PATCH 1/6] xen/tasklet: Fix return value truncation on arm64

2019-12-08 Thread Julien Grall
Hi Andrew, On 05/12/2019 22:30, Andrew Cooper 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(). Introduce a new arch_hypercall

Re: [Xen-devel] [PATCH 2/6] xen/tasklet: Switch data parameter from unsigned long to void *.

2019-12-08 Thread Julien Grall
Hi Andrew, On 05/12/2019 22:30, Andrew Cooper wrote: Most users pass a vcpu pointer, and only stopmachine_action() takes an integer parameter. Switch to using void * to substantially reduce the number of explicit casts. No functional change. Signed-off-by: Andrew Cooper Acked-by: Julien Gr

Re: [Xen-devel] [PATCH 3/6] xen/domctl: Consolidate hypercall continuation handling at the top level

2019-12-08 Thread Julien Grall
Hi, On 05/12/2019 22:30, Andrew Cooper wrote: More paths are going start using hypercall continuations. We could add extra calls to hypercall_create_continuation() but it is much easier to handle -ERESTART once at the top level. One complication is XEN_DOMCTL_shadow_op, which for XSA-97 and AB

Re: [Xen-devel] [PATCH 4/6] xen/hypercall: Cope with -ERESTART on more hypercall paths

2019-12-08 Thread Julien Grall
Hi Andrew, On 05/12/2019 22:30, Andrew Cooper wrote: These hypercalls each use continue_hypercall_on_cpu(), whose API is about to switch to use -ERESTART. Update the soon-to-be affected paths to cope, folding existing contination logic where applicable. In addition: * For platform op and sys

[Xen-devel] [tip: sched/urgent] sched/rt, xen: Use CONFIG_PREEMPTION

2019-12-08 Thread tip-bot2 for Thomas Gleixner
The following commit has been merged into the sched/urgent branch of tip: Commit-ID: d4a3dcbc4727966a64a64d57e2b5106a138d426d Gitweb: https://git.kernel.org/tip/d4a3dcbc4727966a64a64d57e2b5106a138d426d Author:Thomas Gleixner AuthorDate:Tue, 15 Oct 2019 21:18:09 +02:00 Comm

Re: [Xen-devel] [PATCH v2 10/14] driver: xen: Replace cpu_up/down with device_online/offline

2019-12-08 Thread Jürgen Groß
On 25.11.19 12:27, Qais Yousef wrote: The core device API performs extra housekeeping bits that are missing from directly calling cpu_up/down. See commit a6717c01ddc2 ("powerpc/rtas: use device model APIs and serialization during LPM") for an example description of what might go wrong. This als