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

flight 140601 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/140601/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-examine 8 reboot fail REGR. vs. 133580

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

flight 140593 linux-4.14 real [real] http://logs.test-lab.xenproject.org/osstest/logs/140593/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-raw7 xen-boot fail REGR. vs. 139910 test-amd64-i386-xl

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

flight 140598 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/140598/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 139829 test-armhf-armhf-libvirt-raw 13

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

flight 140588 linux-4.19 real [real] http://logs.test-lab.xenproject.org/osstest/logs/140588/ 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 are

[Xen-devel] [seabios test] 140590: tolerable FAIL - PUSHED

flight 140590 seabios real [real] http://logs.test-lab.xenproject.org/osstest/logs/140590/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 138627 test-amd64-amd64-xl-qemuu-ws16-amd64 17

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

flight 140583 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/140583/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 140282

[Xen-devel] [linux-4.4 test] 140577: regressions - FAIL

flight 140577 linux-4.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/140577/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail in 140537 REGR. vs. 139698

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

flight 140574 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/140574/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail REGR. vs. 139876 Tests which are

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

flight 140571 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/140571/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-examine 8 reboot fail REGR. vs. 133580

[Xen-devel] [RFC PATCH v2 1/3] x86/mm/tlb: Change __flush_tlb_one_user interface

__flush_tlb_one_user() currently flushes a single entry, and flushes it both in the kernel and user page-tables, when PTI is enabled. Change __flush_tlb_one_user() and related interfaces into __flush_tlb_range() that flushes a range and does not flush the user page-table. This refactoring is

[Xen-devel] [PATCH v4 0/9] x86/tlb: Concurrent TLB flushes

[ Similar cover-letter to v3 with updated performance numbers on skylake. Sorry for the time it since the last version. ] Currently, local and remote TLB flushes are not performed concurrently, which introduces unnecessary overhead - each PTE flushing can take 100s of cycles. This patch-set

[Xen-devel] [PATCH v4 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently

To improve TLB shootdown performance, flush the remote and local TLBs concurrently. Introduce flush_tlb_multi() that does so. Introduce paravirtual versions of flush_tlb_multi() for KVM, Xen and hyper-v (Xen and hyper-v are only compile-tested). While the updated smp infrastructure is capable of