On Sat, May 19, 2018 at 12:44 PM, Marc Zyngier <marc.zyngier@xxxxxxx> wrote: > That would definitely be the right thing to do. Make sure you (or > Andrey tests with the latest released mainline kernel (4.16 for now) > or (even better) the tip of Linus' tree. Hi! I can confirm that after applying this patch onto 4.17-rc4 kernel the Odroid C2 board that I have boots (it doesn't without the patch). This is the result of running KVM tests that I was able to find [1]: root@odroid64:/home/odroid/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 (5 tests) PASS pci-test (1 tests) FAIL pmu (3 tests, 3 unexpected failures) PASS gicv2-ipi (3 tests) SKIP gicv3-ipi (qemu-system-aarch64: Initialization of device kvm-arm-gicv3 failed: error creating in-kernel VGIC: No such device) PASS gicv2-active (1 tests) SKIP gicv3-active (qemu-system-aarch64: Initialization of device kvm-arm-gicv3 failed: error creating in-kernel VGIC: No such device) PASS psci (4 tests) PASS timer (8 tests) Here is the result of running the same tests on GCC compiled kernel (looks the same): root@odroid64:/home/odroid/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 (5 tests) PASS pci-test (1 tests) FAIL pmu (3 tests, 3 unexpected failures) PASS gicv2-ipi (3 tests) SKIP gicv3-ipi (qemu-system-aarch64: Initialization of device kvm-arm-gicv3 failed: error creating in-kernel VGIC: No such device) PASS gicv2-active (1 tests) SKIP gicv3-active (qemu-system-aarch64: Initialization of device kvm-arm-gicv3 failed: error creating in-kernel VGIC: No such device) PASS psci (4 tests) PASS timer (8 tests) Tested-by: Andrey Konovalov <andreyknvl@xxxxxxxxxx> Thanks! [1] https://www.linux-kvm.org/page/KVM-unit-tests _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm