On Sun, 2018-07-29 at 13:47 +0200, Mike Galbraith wrote: > FYI, per kvm unit tests, 4.16-rt definitely has more kvm issues. > > huawei5:/abuild/mike/kvm-unit-tests # uname -r > 4.16.18-rt11-rt > huawei5:/abuild/mike/kvm-unit-tests # ./run_tests.sh > PASS selftest-setup (2 tests) > FAIL selftest-vectors-kernel > FAIL selftest-vectors-user > PASS selftest-smp (65 tests) > PASS pci-test (1 tests) > PASS pmu (3 tests) > FAIL gicv2-ipi > FAIL gicv3-ipi > FAIL gicv2-active > FAIL gicv3-active > PASS psci (4 tests) > FAIL timer > huawei5:/abuild/mike/kvm-unit-tests # > > 4.14-rt passes all tests. The above is with the kvm raw_spinlock_t > conversion patch applied, but the 4.12 based SLERT tree I cloned to > explore arm-land in the first place shows only one timer failure, and > has/needs it applied as well, which would seem to vindicate it. > > huawei5:/abuild/mike/kvm-unit-tests # uname -r > 4.12.14-0.gec0b559-rt > huawei5:/abuild/mike/kvm-unit-tests # ./run_tests.sh > PASS selftest-setup (2 tests) > PASS selftest-vectors-kernel (2 tests) > PASS selftest-vectors-user (2 tests) > PASS selftest-smp (65 tests) > PASS pci-test (1 tests) > PASS pmu (3 tests) > PASS gicv2-ipi (3 tests) > PASS gicv3-ipi (3 tests) > PASS gicv2-active (1 tests) > PASS gicv3-active (1 tests) > PASS psci (4 tests) > FAIL timer (8 tests, 1 unexpected failures) FWIW, this single timer failure wass inspired by something in the 4-15 merge window. A 4.14-rt based 4.15-rt updated to include recent fixes reproduces the exact same (ie my colleagues imported it into SLE). The rest landed in 4.16.. staring at which is not proving the least bit enlightening. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
