[Xen-devel] [xen-unstable-smoke test] 122083: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122083 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122083/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

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

2018-04-08 Thread osstest service owner
flight 122084 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/122084/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 121769 build-amd64-xsm

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

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

[Xen-devel] [xen-unstable-smoke test] 122087: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122087 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122087/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

[Xen-devel] [ovmf bisection] complete build-i386

2018-04-08 Thread osstest service owner
branch xen-unstable xenbranch xen-unstable job build-i386 testid xen-build Tree: ovmf https://github.com/tianocore/edk2.git Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git Tree: qemuu git://xenbits.xen.org/qemu-xen.git Tree: xen git://xenbits.xen.org/xen.git *** Found and reproduced pro

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

2018-04-08 Thread osstest service owner
flight 122043 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/122043/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-multivcpu 5 host-ping-check-nativefail pass in 121974 test-armhf-armhf-libvirt-xsm 6

[Xen-devel] [PATCH v2 4/7] add nspin_sleep function to time manager

2018-04-08 Thread Paul Semel
From: Paul Semel Signed-off-by: Paul Semel --- common/time.c | 9 + 1 file changed, 9 insertions(+) diff --git a/common/time.c b/common/time.c index 1f0f289..1d7fef5 100644 --- a/common/time.c +++ b/common/time.c @@ -110,6 +110,15 @@ int gettimeofday(struct timeval *tp) return 0;

[Xen-devel] [PATCH v2 2/7] add current_time function to time manager

2018-04-08 Thread Paul Semel
From: Paul Semel this function returns the "epoch" time Signed-off-by: Paul Semel --- common/time.c | 18 ++ include/xtf/time.h | 2 ++ 2 files changed, 20 insertions(+) diff --git a/common/time.c b/common/time.c index a0f53bf..3e8e8ce 100644 --- a/common/time.c +++ b/co

[Xen-devel] [PATCH v2 3/7] add gettimeofday function to time managment

2018-04-08 Thread Paul Semel
From: Paul Semel Signed-off-by: Paul Semel --- common/time.c | 23 +++ include/xtf/time.h | 7 +++ 2 files changed, 30 insertions(+) diff --git a/common/time.c b/common/time.c index 3e8e8ce..1f0f289 100644 --- a/common/time.c +++ b/common/time.c @@ -87,6 +87,29 @@

[Xen-devel] [PATCH v2 6/7] add mspin_sleep function to time manager

2018-04-08 Thread Paul Semel
From: Paul Semel Signed-off-by: Paul Semel --- common/time.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/common/time.c b/common/time.c index 67fe049..f75979a 100644 --- a/common/time.c +++ b/common/time.c @@ -125,6 +125,12 @@ static inline void spin_sleep(uint64_t t) nspin_sl

[Xen-devel] [PATCH v2 5/7] add spin_sleep function to time manager

2018-04-08 Thread Paul Semel
From: Paul Semel Signed-off-by: Paul Semel --- common/time.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/common/time.c b/common/time.c index 1d7fef5..67fe049 100644 --- a/common/time.c +++ b/common/time.c @@ -119,6 +119,12 @@ static inline void nspin_sleep(uint64_t t) cur

[Xen-devel] [PATCH v2 1/7] introduce time managment in xtf

2018-04-08 Thread Paul Semel
From: Paul Semel this file is introduce to be able to implement an inter domain communication protocol over xenstore. For synchronization purpose, we do really want to be able to "control" time common/time.c: since_boot_time gets the time in nanoseconds from the moment the VM has booted Signed-

[Xen-devel] [PATCH v2 7/7] add sleep, msleep and NOW() macros to time manager

2018-04-08 Thread Paul Semel
From: Paul Semel Signed-off-by: Paul Semel --- common/time.c | 10 ++ include/xtf/time.h | 12 2 files changed, 22 insertions(+) diff --git a/common/time.c b/common/time.c index f75979a..246a2dd 100644 --- a/common/time.c +++ b/common/time.c @@ -131,6 +131,16 @@ stati

[Xen-devel] [xen-unstable-smoke test] 122097: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122097 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122097/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

[Xen-devel] [PATCH v2 (fix)] introduce time managment in xtf

2018-04-08 Thread Paul Semel
From: Paul Semel this file is introduce to be able to implement an inter domain communication protocol over xenstore. For synchronization purpose, we do really want to be able to "control" time common/time.c: since_boot_time gets the time in nanoseconds from the moment the VM has booted Signed-

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

2018-04-08 Thread osstest service owner
flight 122092 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/122092/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf e037e88cd81d4ac63dd627719c87c305bf0b439e baseline version: ovmf aae02dccf5b0ad07e60d2

Re: [Xen-devel] [PATCH 1/7] introduce time managment in xtf

2018-04-08 Thread Paul Semel
On 04/07/2018 10:58 PM, Paul Semel wrote: On 04/07/2018 10:39 PM, Andrew Cooper wrot> However, both of your patches have (different) barrier issues, and different (mis)uses of the shared memory clocks, which will need to be addressed. One general comment for the full series is to not bother

[Xen-devel] [xen-unstable baseline-only test] 74558: regressions - trouble: blocked/broken/fail/pass

2018-04-08 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 74558 xen-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/74558/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64

Re: [Xen-devel] [PATCH 1/7] introduce time managment in xtf

2018-04-08 Thread Andrew Cooper
On 08/04/2018 15:00, Paul Semel wrote: > On 04/07/2018 10:58 PM, Paul Semel wrote: >> On 04/07/2018 10:39 PM, Andrew Cooper wrot> However, both of your >> patches have (different) barrier issues, and >>> different (mis)uses of the shared memory clocks, which will need >>> to be >>>

[Xen-devel] [xen-unstable-smoke test] 122106: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122106 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122106/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

[Xen-devel] [ovmf baseline-only test] 74561: all pass

2018-04-08 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 74561 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/74561/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf e037e88cd81d4ac63dd627719c87c305bf0b439e baseline v

[Xen-devel] [xen-unstable-smoke test] 122107: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122107 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122107/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

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

2018-04-08 Thread osstest service owner
flight 122094 linux-3.18 real [real] http://logs.test-lab.xenproject.org/osstest/logs/122094/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-debianhvm-amd64 16 guest-localmigrate/x10 fail REGR. vs. 121320 build-ar

[Xen-devel] [xen-4.6-testing baseline-only test] 74559: trouble: broken/fail/pass

2018-04-08 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 74559 xen-4.6-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/74559/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-xtf-amd64-amd64-1

[Xen-devel] Weird altp2m behaviour when switching early to a new view

2018-04-08 Thread Razvan Cojocaru
Hello, I've noticed altp2m behaviour I can't explain yet - I'm not all that familiar with all the ways the new views corellate with the previous EPT-based "view 0". In short, if we create a new view and simply switch to it early in the boot process of the guest, something goes wrong and the guest

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

2018-04-08 Thread osstest service owner
flight 122067 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/122067/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-xsm7 xen-boot fail REGR. vs. 118324 test-amd64-i386-xl-

[Xen-devel] [xen-unstable-smoke test] 122108: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122108 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122108/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

[Xen-devel] [qemu-mainline test] 122080: trouble: broken/fail/pass

2018-04-08 Thread osstest service owner
flight 122080 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/122080/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl broken Tests which are fai

[Xen-devel] [xen-unstable-smoke test] 122113: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122113 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122113/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

[Xen-devel] [xen-unstable-smoke test] 122117: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122117 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122117/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

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

2018-04-08 Thread osstest service owner
flight 122096 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/122096/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-ws16-amd64 16 guest-localmigrate/x10 fail like 121522 test-amd64-i386-xl-qemut-win7-amd64 17

[Xen-devel] [xen-unstable-smoke test] 122119: regressions - FAIL

2018-04-08 Thread osstest service owner
flight 122119 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122119/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 121876 build-armhf

Re: [Xen-devel] [PATCH v5 7/7] xen/x86: use PCID feature

2018-04-08 Thread Juergen Gross
On 06/04/18 19:30, Andrew Cooper wrote: > On 06/04/18 08:52, Juergen Gross wrote: >> Avoid flushing the complete TLB when switching %cr3 for mitigation of >> Meltdown by using the PCID feature if available. >> >> We are using 4 PCID values for a 64 bit pv domain subject to XPTI and >> 2 values for