Re: [Xen-devel] [PATCH -next] drm/xen-front: Drop pointless static qualifier in fb_destroy()

2019-02-03 Thread Oleksandr Andrushchenko
On 1/26/19 2:05 PM, YueHaibing wrote: > There is no need to have the 'struct drm_framebuffer *fb' variable > static since new value always be assigned before use it. > > Signed-off-by: YueHaibing > --- > drivers/gpu/drm/xen/xen_drm_front_kms.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletio

Re: [Xen-devel] [PATCH] drm/xen-front: Fix mmap attributes for display buffers

2019-02-03 Thread Oleksandr Andrushchenko
On 1/29/19 9:07 PM, Julien Grall wrote: > Hi Oleksandr, > > On 1/29/19 3:04 PM, Oleksandr Andrushchenko wrote: >> From: Oleksandr Andrushchenko >> >> When GEM backing storage is allocated those are normal pages, >> so there is no point using pgprot_writecombine while mmaping. >> This fixes mismatc

[Xen-devel] [xen-unstable test] 132759: tolerable FAIL - PUSHED

2019-02-03 Thread osstest service owner
flight 132759 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/132759/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-i386-rumprun-i386 17 rumprun-demo-xenstorels/xenstorels.repeat fail REGR. vs. 132622 Tests whi

Re: [Xen-devel] [PATCH] tools/misc: Remove obsolete xen-bugtool

2019-02-03 Thread Juergen Gross
On 03/02/2019 21:35, Hans van Kranenburg wrote: > xen-bugtool relies on code that has been removed in commit 9e8672f1c3 > "tools: remove xend and associated python modules", more than 5 years > ago. Remove it, since it confuses users. > > -$ /usr/sbin/xen-bugtool > Traceback (most recent c

[Xen-devel] [xen-4.10-testing test] 132762: regressions - FAIL

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

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

2019-02-03 Thread osstest service owner
flight 132766 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/132766/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 6c61ec4c62b6d1001e8ea6683e83f0e9ec0b3c9b baseline version: ovmf 7381bd3e753c4d3b706c7

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

2019-02-03 Thread osstest service owner
flight 132754 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/132754/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-examine 4 memdisk-try-append fail REGR. vs. 132599 Regressions which a

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

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

[Xen-devel] [linux-4.9 test] 132748: tolerable FAIL - PUSHED

2019-02-03 Thread osstest service owner
flight 132748 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/132748/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 132521 test-amd64-i386-xl-qemut-win7-amd64 17

[Xen-devel] [linux-3.18 bisection] complete test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm

2019-02-03 Thread osstest service owner
branch xen-unstable xenbranch xen-unstable job test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm testid xen-boot Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.

[Xen-devel] [PATCH] tools/misc: Remove obsolete xen-bugtool

2019-02-03 Thread Hans van Kranenburg
xen-bugtool relies on code that has been removed in commit 9e8672f1c3 "tools: remove xend and associated python modules", more than 5 years ago. Remove it, since it confuses users. -$ /usr/sbin/xen-bugtool Traceback (most recent call last): File "/usr/sbin/xen-bugtool", line 9, in

Re: [Xen-devel] [PATCH v7 10/15] argo: implement the notify op

2019-02-03 Thread Christopher Clark
On Thu, Jan 31, 2019 at 8:45 AM Roger Pau Monné wrote: > > On Wed, Jan 30, 2019 at 08:28:15PM -0800, Christopher Clark wrote: > > Queries for data about space availability in registered rings and > > causes notification to be sent when space has become available. > > > > The hypercall op populates

Re: [Xen-devel] [PATCH v7 09/15] argo: implement the sendv op; evtchn: expose send_guest_global_virq

2019-02-03 Thread Christopher Clark
On Thu, Jan 31, 2019 at 8:38 AM Roger Pau Monné wrote: > > On Wed, Jan 30, 2019 at 08:28:14PM -0800, Christopher Clark wrote: > > sendv operation is invoked to perform a synchronous send of buffers > > contained in iovs to a remote domain's registered ring. > > > > It takes: > > * A destination a

Re: [Xen-devel] [PATCH v7 07/15] argo: implement the register op

2019-02-03 Thread Christopher Clark
n Thu, Jan 31, 2019 at 8:19 AM Roger Pau Monné wrote: > > On Wed, Jan 30, 2019 at 08:28:12PM -0800, Christopher Clark wrote: > > The register op is used by a domain to register a region of memory for > > receiving messages from either a specified other domain, or, if specifying a > > wildcard, any

Re: [Xen-devel] [PATCH v5 00/15] Argo: hypervisor-mediated interdomain communication

2019-02-03 Thread Christopher Clark
On Thu, Jan 31, 2019 at 5:39 AM Roger Pau Monné wrote: > > On Wed, Jan 30, 2019 at 08:05:30PM -0800, Christopher Clark wrote: > > On Tue, Jan 22, 2019 at 6:19 AM Roger Pau Monné > > wrote: > > > > > > On Mon, Jan 21, 2019 at 01:59:40AM -0800, Christopher Clark wrote: > > > > Version five of this

Re: [Xen-devel] [PATCH v7 04/15] argo: init, destroy and soft-reset, with enable command line opt

2019-02-03 Thread Christopher Clark
On Thu, Jan 31, 2019 at 6:49 AM Roger Pau Monné wrote: > > On Wed, Jan 30, 2019 at 08:28:09PM -0800, Christopher Clark wrote: > > Initialises basic data structures and performs teardown of argo state > > for domain shutdown. > > > > Inclusion of the Argo implementation is dependent on CONFIG_ARGO.

Re: [Xen-devel] [PATCH v5 09/15] argo: implement the sendv op; evtchn: expose send_guest_global_virq

2019-02-03 Thread Christopher Clark
On Thu, Jan 31, 2019 at 3:01 AM Roger Pau Monné wrote: > > On Thu, Jan 31, 2019 at 03:35:23AM -0700, Jan Beulich wrote: > > >>> On 31.01.19 at 11:18, wrote: > > > On Wed, Jan 30, 2019 at 08:10:28PM -0800, Christopher Clark wrote: > > >> On Tue, Jan 22, 2019 at 4:08 AM Roger Pau Monné > > >> wro

[Xen-devel] [xen-4.9-testing test] 132747: regressions - FAIL

2019-02-03 Thread osstest service owner
flight 132747 xen-4.9-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/132747/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 130954 build-amd64-xsm

[Xen-devel] [xen-4.11-testing test] 132736: regressions - FAIL

2019-02-03 Thread osstest service owner
flight 132736 xen-4.11-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/132736/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-ws16-amd64 13 guest-saverestore fail REGR. vs. 132647 Regressions wh

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

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

[Xen-devel] [qemu-mainline test] 132737: regressions - FAIL

2019-02-03 Thread osstest service owner
flight 132737 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/132737/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-arndale 6 xen-install fail REGR. vs. 131842 test-amd64-amd64-

[Xen-devel] [linux-4.19 test] 132732: regressions - trouble: blocked/broken/fail/pass

2019-02-03 Thread osstest service owner
flight 132732 linux-4.19 real [real] http://logs.test-lab.xenproject.org/osstest/logs/132732/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-libvirt broken test-amd64-amd64-xl-qemut-stubdom-debianhvm

[Xen-devel] [xen-unstable-coverity test] 132767: regressions - ALL FAIL

2019-02-03 Thread osstest service owner
flight 132767 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/132767/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: coverity-amd647 coverity-upload fail REGR. vs. 132424 version t

Re: [Xen-devel] [PATCH v2 10/21] memblock: refactor internal allocation functions

2019-02-03 Thread Mike Rapoport
On Sun, Feb 03, 2019 at 08:39:20PM +1100, Michael Ellerman wrote: > Mike Rapoport writes: > > > Currently, memblock has several internal functions with overlapping > > functionality. They all call memblock_find_in_range_node() to find free > > memory and then reserve the allocated range and mark

Re: [Xen-devel] [PATCH v2 10/21] memblock: refactor internal allocation functions

2019-02-03 Thread Michael Ellerman
Mike Rapoport writes: > Currently, memblock has several internal functions with overlapping > functionality. They all call memblock_find_in_range_node() to find free > memory and then reserve the allocated range and mark it with kmemleak. > However, there is difference in the allocation constrain