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

2017-03-11 Thread osstest service owner
flight 106609 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/106609/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvops 5 kernel-build fail REGR. vs. 59254 build-i386-pvops

[Xen-devel] [distros-debian-jessie test] 68668: trouble: blocked/broken/pass

2017-03-11 Thread Platform Team regression test user
flight 68668 distros-debian-jessie real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68668/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops 3 host-install(3) broken REG

[Xen-devel] [ovmf test] 106601: regressions - FAIL

2017-03-11 Thread osstest service owner
flight 106601 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/106601/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 105963 test-amd64-i386-xl-qemuu-

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

2017-03-11 Thread osstest service owner
flight 106600 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/106600/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254 test-armhf-armhf-xl

[Xen-devel] [qemu-upstream-4.8-testing baseline-only test] 68666: tolerable trouble: blocked/broken/fail/pass

2017-03-11 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 68666 qemu-upstream-4.8-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68666/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-arm64-arm64-libvirt-xsm 1 bu

[Xen-devel] [ovmf test] 106598: regressions - FAIL

2017-03-11 Thread osstest service owner
flight 106598 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/106598/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 105963 test-amd64-i386-xl-qemuu-

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

2017-03-11 Thread osstest service owner
flight 106597 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/106597/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254 test-armhf-armhf-xl

[Xen-devel] [qemu-upstream-4.7-testing baseline-only test] 68665: tolerable trouble: blocked/broken/fail/pass

2017-03-11 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 68665 qemu-upstream-4.7-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68665/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-arm64-arm64-libvirt-xsm 1 bu

[Xen-devel] [xen-4.8-testing baseline-only test] 68657: tolerable trouble: blocked/broken/fail/pass

2017-03-11 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 68657 xen-4.8-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68657/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-arm64-arm64-libvirt-xsm 1 build-check(

Re: [Xen-devel] Mapping active GDT

2017-03-11 Thread Andrew Cooper
On 11/03/2017 03:58, Boris Ostrovsky wrote: > On 03/10/2017 09:39 PM, Boris Ostrovsky wrote: >> I am looking into GDT remap series [0] which crashes PV guests and it >> seems that the problem lies in the fact that we cannot establish new >> mapping to an already existing GDT. >> >> The mapping is c

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

2017-03-11 Thread osstest service owner
flight 106593 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/106593/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail pass in 106584 test-armhf-armhf-xl-rtds 15

[Xen-devel] [xen-4.7-testing baseline-only test] 68656: tolerable trouble: blocked/broken/fail/pass

2017-03-11 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 68656 xen-4.7-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68656/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-arm64-arm64-libvirt-xsm 1 build-check(

[Xen-devel] [ovmf test] 106592: regressions - FAIL

2017-03-11 Thread osstest service owner
flight 106592 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/106592/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 105963 test-amd64-i386-xl-qemuu-

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

2017-03-11 Thread osstest service owner
flight 106591 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/106591/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254 test-armhf-armhf-xl

Re: [Xen-devel] [PATCH v7 3/5] x86/ioreq server: Handle read-modify-write cases for p2m_ioreq_server pages.

2017-03-11 Thread Yu Zhang
On 3/10/2017 11:33 PM, Jan Beulich wrote: On 08.03.17 at 16:33, wrote: @@ -197,6 +217,10 @@ static int hvmemul_do_io( * - If the IOREQ_MEM_ACCESS_WRITE flag is not set, treat it * like a normal PIO or MMIO that doesn't have an ioreq * server (i.e., by ig

Re: [Xen-devel] [PATCH v7 5/5] x86/ioreq server: Synchronously reset outstanding p2m_ioreq_server entries when an ioreq server unmaps.

2017-03-11 Thread Yu Zhang
On 3/11/2017 12:17 AM, Jan Beulich wrote: On 08.03.17 at 16:33, wrote: --- a/xen/arch/x86/hvm/dm.c +++ b/xen/arch/x86/hvm/dm.c @@ -288,6 +288,7 @@ static int inject_event(struct domain *d, return 0; } +#define DMOP_op_mask 0xff static int dm_op(domid_t domid, Please follow the

Re: [Xen-devel] [PATCH v7 5/5] x86/ioreq server: Synchronously reset outstanding p2m_ioreq_server entries when an ioreq server unmaps.

2017-03-11 Thread Yu Zhang
On 3/11/2017 12:59 AM, Andrew Cooper wrote: On 08/03/17 15:33, Yu Zhang wrote: After an ioreq server has unmapped, the remaining p2m_ioreq_server entries need to be reset back to p2m_ram_rw. This patch does this synchronously by iterating the p2m table. The synchronous resetting is necessary

Re: [Xen-devel] [PATCH v7 4/5] ix86/ioreq server: Asynchronously reset outstanding p2m_ioreq_server entries.

2017-03-11 Thread Yu Zhang
On 3/11/2017 12:03 AM, Jan Beulich wrote: On 08.03.17 at 16:33, wrote: --- a/xen/arch/x86/mm/p2m.c +++ b/xen/arch/x86/mm/p2m.c @@ -954,6 +954,26 @@ int p2m_change_type_one(struct domain *d, unsigned long gfn, p2m->default_access) : -EBUSY; +if ( !

Re: [Xen-devel] [PATCH v7 2/5] x86/ioreq server: Add DMOP to map guest ram with p2m_ioreq_server to an ioreq server.

2017-03-11 Thread Yu Zhang
On 3/10/2017 11:29 PM, Jan Beulich wrote: On 08.03.17 at 16:33, wrote: changes in v7: - Use new ioreq server interface - XEN_DMOP_map_mem_type_to_ioreq_server. - According to comments from George: removed domain_pause/unpause() in hvm_map_mem_type_to_ioreq_server(), because it's to

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

2017-03-11 Thread osstest service owner
flight 106594 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/106594/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt-xsm 5 xen-install fail REGR. vs. 106562 Regressions which are r