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

2019-06-02 Thread osstest service owner
flight 137170 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/137170/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen 0e623fad00d84f7051950cb35db06bd038c9 baseline version: xen 9abc

[Xen-devel] [linux-4.14 test] 137112: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137112 linux-4.14 real [real] http://logs.test-lab.xenproject.org/osstest/logs/137112/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 12 guest-start/debianhvm.repeat fail REGR. vs.

[Xen-devel] [PATCH v2] xen/arm: irq: Don't use _IRQ_PENDING when handling host interrupt

2019-06-02 Thread Julien Grall
While SPIs are shared between CPU, it is not possible to receive the same interrupts on a different CPU while the interrupt is in active state. For host interrupt (i.e routed to Xen), the deactivation of the interrupt is done at the end of the handling. This can alternatively be done outside of th

Re: [Xen-devel] [PATCH] xen/public: arch-arm: Restrict the visibility of struct vcpu_guest_core_regs

2019-06-02 Thread Julien Grall
Hi Artem, On 5/22/19 7:05 PM, Artem Mygaiev wrote: On Wed, 2019-05-22 at 14:00 +0100, Julien Grall wrote: On 22/05/2019 13:29, Jan Beulich wrote: On 22.05.19 at 14:20, < julien.gr...@arm.com wrote: On 21/05/2019 10:55, Julien Grall wrote: Hi Jan, On 5/21/19 10:43 AM, Jan Beulich wrote: On

[Xen-devel] [linux-3.18 test] 137110: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137110 linux-3.18 real [real] http://logs.test-lab.xenproject.org/osstest/logs/137110/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-credit2 7 xen-boot fail REGR. vs. 128858 test-amd64-amd64-xl-

[Xen-devel] [linux-4.9 test] 137113: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137113 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/137113/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-examine11 examine-serial/bootloader fail REGR. vs. 136967 Tests which did not s

[Xen-devel] [PATCH v2] xen/arm: Black list everything with a PPI

2019-06-02 Thread Amit Singh Tomar
XEN should not forward PPIs to Dom0 as it only support SPIs. One of solution to this problem is to skip any device that uses PPI source completely while building domain itself. This patch goes through all the interrupt sources of device and skip it if one of interrupt source is PPI. It fixes XEN b

[Xen-devel] [xen-4.8-testing test] 137114: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137114 xen-4.8-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/137114/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-prev 6 xen-buildfail REGR. vs. 130965 build-i386-prev

[Xen-devel] [ovmf test] 137118: all pass - PUSHED

2019-06-02 Thread osstest service owner
flight 137118 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/137118/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 8594c2073cdb1065e60f01e9b099918c5e839212 baseline version: ovmf 5a9e23ceb991f3bd0eea7

Re: [Xen-devel] [PATCH net-next] Update my email address

2019-06-02 Thread David Miller
From: Wei Liu Date: Fri, 31 May 2019 08:31:02 +0100 > Signed-off-by: Wei Liu Applied. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [xen-unstable test] 137115: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137115 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/137115/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-examine11 examine-serial/bootloader fail REGR. vs. 137033 Tests which did no

[Xen-devel] [libvirt test] 137120: tolerable all pass - PUSHED

2019-06-02 Thread osstest service owner
flight 137120 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/137120/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 137099 test-armhf-armhf-libvirt-raw 13 saveresto

[Xen-devel] [linux-4.19 test] 137119: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137119 linux-4.19 real [real] http://logs.test-lab.xenproject.org/osstest/logs/137119/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops 6 kernel-build fail REGR. vs. 129313 Tests which did not

Re: [Xen-devel] [PATCH] xen: notifier: refine 'notifier_head', use 'list_head' directly

2019-06-02 Thread chenbaodong
On 5/31/19 18:22, Julien Grall wrote: Hi, Missing commit message here. Yes, will be added. On 5/31/19 3:35 AM, Baodong Chen wrote: Signed-off-by: Baodong Chen ---   xen/common/notifier.c  | 25 ++---   xen/include/xen/notifier.h | 21 +++--   2 files c

[Xen-devel] [PATCH RESEND] xen: notifier: refine 'notifier_head', use 'list_head' directly

2019-06-02 Thread Baodong Chen
'notifier_block' can be replaced with 'list_head' when used for 'notifier_head', this make the a little more clear. Signed-off-by: Baodong Chen --- xen/common/notifier.c | 12 ++-- xen/include/xen/notifier.h | 7 +++ 2 files changed, 9 insertions(+), 10 deletions(-) diff --git

Re: [Xen-devel] [PATCH] xen: put cpupool's member 'n_dom' after 'cpupool_id'

2019-06-02 Thread chenbaodong
On 5/31/19 18:52, Julien Grall wrote: Hi, On 5/31/19 4:18 AM, Baodong Chen wrote: Thus, sizeof(struct cpupool) will save 8 bytes for 64-bit system. I am happy with the change, although AFAIK cpupool is not instantiated that often. Are you planning to have more instantiation of it? Cheers,

Re: [Xen-devel] [PATCH] xen: cpu: change 'cpu_hotplug_[begin|done]' to inline function

2019-06-02 Thread chenbaodong
On 5/31/19 18:55, Julien Grall wrote: Hi, On 5/31/19 3:46 AM, Baodong Chen wrote: Signed-off-by: Baodong Chen ---   xen/common/cpu.c  | 10 --   xen/include/xen/cpu.h |  4 ++--   2 files changed, 2 insertions(+), 12 deletions(-) diff --git a/xen/common/cpu.c b/xen/common/cpu.c ind

Re: [Xen-devel] [PATCH] xen: cpu: change 'cpu_hotplug_[begin|done]' to inline function

2019-06-02 Thread chenbaodong
On 5/31/19 19:30, Jan Beulich wrote: On 31.05.19 at 12:55, wrote: On 5/31/19 3:46 AM, Baodong Chen wrote: --- a/xen/include/xen/cpu.h +++ b/xen/include/xen/cpu.h @@ -10,8 +10,8 @@ bool_t get_cpu_maps(void); void put_cpu_maps(void); /* Safely perform CPU hotplug and update cpu_online

[Xen-devel] [PATCH RESEND] xen: cpu: change 'cpu_hotplug_[begin|done]' to inline function

2019-06-02 Thread Baodong Chen
Signed-off-by: Baodong Chen --- xen/common/cpu.c | 10 -- xen/include/xen/cpu.h | 10 -- 2 files changed, 8 insertions(+), 12 deletions(-) diff --git a/xen/common/cpu.c b/xen/common/cpu.c index f388d89..a526b55 100644 --- a/xen/common/cpu.c +++ b/xen/common/cpu.c @@ -51,16 +

Re: [Xen-devel] [PATCH] xen: make tracebuffer configurable

2019-06-02 Thread chenbaodong
On 5/31/19 19:10, Jan Beulich wrote: On 30.05.19 at 12:17, wrote: Default: enabled. Can be disabled for smaller code footprint. But you're aware that we're, for now at least, trying to limit the number of independently selectable config options? Ones depending on EXPERT are sort of an excepti

Re: [Xen-devel] [PATCH] xen: make tracebuffer configurable

2019-06-02 Thread chenbaodong
On 5/31/19 20:58, George Dunlap wrote: On May 31, 2019, at 12:10 PM, Jan Beulich wrote: On 30.05.19 at 12:17, wrote: Default: enabled. Can be disabled for smaller code footprint. But you're aware that we're, for now at least, trying to limit the number of independently selectable config

Re: [Xen-devel] [PATCH] xen: make keyhanler configurable

2019-06-02 Thread chenbaodong
On 5/31/19 18:39, Dario Faggioli wrote: On Fri, 2019-05-31 at 09:58 +0800, Baodong Chen wrote: keyhandler mainly used for debug usage by developers which can dump xen module(eg. timer, scheduler) status at runtime by input character from console. Signed-off-by: Baodong Chen --- --- a/xen/comm

Re: [Xen-devel] [PATCH] xen: make keyhanler configurable

2019-06-02 Thread chenbaodong
On 5/31/19 18:53, Juergen Gross wrote: On 31/05/2019 03:58, Baodong Chen wrote: keyhandler mainly used for debug usage by developers which can dump xen module(eg. timer, scheduler) status at runtime by input character from console. Signed-off-by: Baodong Chen --- xen/arch/arm/gic.c

Re: [Xen-devel] [PATCH] xen: make keyhanler configurable

2019-06-02 Thread chenbaodong
On 6/1/19 06:30, Andrew Cooper wrote: On 30/05/2019 18:58, Baodong Chen wrote: keyhandler mainly used for debug usage by developers which can dump xen module(eg. timer, scheduler) status at runtime by input character from console. Signed-off-by: Baodong Chen What is the motivation here?  I d

[Xen-devel] [linux-linus test] 137125: regressions - FAIL

2019-06-02 Thread osstest service owner
flight 137125 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/137125/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-examine11 examine-serial/bootloader fail REGR. vs. 133580 build-armhf-pvops