On Mon, 24 Feb 2020 at 23:06, Alexandru Elisei <alexandru.elisei@xxxxxxx> wrote: > > Hi, > > On 2/24/20 4:55 PM, Naresh Kamboju wrote: > > On Mon, 24 Feb 2020 at 20:29, Andrew Jones <drjones@xxxxxxxxxx> wrote: > >> On Mon, Feb 24, 2020 at 01:47:44PM +0000, Alexandru Elisei wrote: > >>> Hi, > >>> > >>> On 2/24/20 1:38 PM, Andrew Jones wrote: > >>>> On Mon, Feb 24, 2020 at 01:21:23PM +0000, Alexandru Elisei wrote: > >>>>> Hi Naresh, > >>>>> > >>>>> On 2/24/20 12:53 PM, Naresh Kamboju wrote: > >>>>>> [..] > >>>>> I am going to comment on the arm64 tests. As far as I am aware, you don't need any > >>>>> kernel configs to run the tests. > > Thanks for the confirmation on Kconfig part for arm64. > > The next question is, How to enable and run nested virtual testing ? > > There's not support in KVM to run nested guests (yet [1]) and no support in > kvm-unit-tests to run at EL2 (yet [2]) and no hardware that has supported for > nested virtualization (yet). ack. > > [1] https://www.spinics.net/lists/arm-kernel/msg784744.html > [2] https://www.spinics.net/lists/kvm/msg203527.html > > > >>>>> From looking at the java log [1], I can point out a few things: > >>>>> > >>>>> - The gicv3 tests are failing because Juno has a gicv2 and the kernel refuses to > >>>>> create a virtual gicv3. It's normal. > > Got it. > > Because of heterogeneous big.LITTLE CPU architecture of Juno device caused > > test hang and "taskset -c 0 ./run_tests.sh -a -v -t " solved this problem. > > KVM doesn't normally care about big.little configurations, and kvm-unit-tests > definitely doesn't do anything that is specific to a certain microarchitecture. I > would say something else is wrong here. I'll try and reproduce it on my Juno when > I get the time, but that might not happen until next week. Can you trigger this > behaviour every run? I will schedule multiple runs and get an answer by tomorrow. > > > > >>>> Yup > > timers test is intermittent failure due to timeout on the CPU 0 which > > is configured > > as LITTLE cpu cortext a53. If i change test to run on big CPU then it > > always PASS. > > "taskset -c $BIG_CPU_ID ./run_tests.sh -a -v -t" > > This might just be an unfortunate mix of events and kernel scheduling decisions > for the VCPU thread that is causing an unexpected delay in receiving timer > interrupts. Hard to know without a log. > > > > >>>>> - I am not familiar with the PMU test, so I cannot help you with that. > >>>> Where is the output from running the PMU test? I didn't see it in the link > >>>> below. > >>> It's toward the end, it just says that 2 tests failed: > >> If the test runner isn't capturing all the output of the tests somewhere, > >> then it should. Naresh, is the pmu.log file somewhere? > > For more detail I have shared LAVA log [1] and attached detail run output. > > > > timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 > > -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device > > virtio-serial-device -device virtconsole,chardev=ctd -chardev > > testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel > > arm/pmu.flat -smp 1 # -initrd /tmp/tmp.ZJ05lRvgc4 > > INFO: PMU version: 3 > > INFO: pmu: PMU implementer/ID code/counters: 0x41(\"A\")/0x3/6 > > PASS: pmu: Control register > > Read 0 then 0. > > FAIL: pmu: Monotonically increasing cycle count > > instrs : cycles0 cycles1 ... > > 4: 0 > > cycles not incrementing! > > FAIL: pmu: Cycle/instruction ratio > > SUMMARY: 3 tests, 2 unexpected failures > > This when running the tests with taskset, right? Right. > > > [..] > > timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 > > -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device > > virtio-serial-device -device virtconsole,chardev=ctd -chardev > > testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel > > arm/micro-bench.flat -smp 2 # -initrd /tmp/tmp.urqlMsBpJd > > Timer Frequency 50000000 Hz (Output in microseconds) > > name total ns avg ns > > -------------------------------------------------------------------------------------------- > > hvc 296915440.0 4530.0 > > mmio_read_user 1322325100.0 20177.0 > > mmio_read_vgic 462255460.0 7053.0 > > eoi 6779880.0 103.0 > > qemu-system-aarch64: terminating on signal 15 from pid 3097 (timeout) > > > > [..] > > I think this is because you are running it on one physical CPU (it's exactly the > same message I am getting when I use taskset to run the tests). Can you try and > run it without taskset and see if it solves your issue? Alright. I will run without taskset and share logs here. > > Thanks, > Alex
