Sorry, just noticed this - you dropped me and the kvmarm list from your reply. On Wed, Nov 20, 2013 at 11:06:11PM +0000, María Soler Heredia wrote: > Andrew Jones <drjones <at> redhat.com> writes: > > > > This series introduces arm to kvm-unit-tests. > > > To use this you need an arm platform or simulator capable > > of running kvmarm and a qemu with the mach-virt patches[2], as > > well as the previously mentioned virtio-testdev. > > Hello, > > I have been playing with your tests for a while and I cannot seem to get > them to work all right. When I run them disabling kvm on the arm-run script, > they do work, but when I run them with kvm enabled they fail. > > This is my output: > > ./arm-run arm/boot.flat -smp 1 -m 256 -append 'info 0x10000000 0x1000' > qemu-system-arm -device virtio-testdev -display none -serial stdio -M virt > -cpu cortex-a15 -enable-kvm -kernel arm/boot.flat -smp 1 -m 256 -append info > 0x10000000 0x1000 > kvm [1252]: load/store instruction decoding not implemented > error: kvm run failed Function not implemented The above errors come from the kernel and qemu. It's easy to see under what condition you would hit them, but it's not clear to me why that condition is present for you. > ./arm-run: line 16: 1251 Aborted $command "$@" > Return value from qemu: 134 > FAIL boot_info > ./arm-run arm/boot.flat -smp 1 -append 'vectors' > qemu-system-arm -device virtio-testdev -display none -serial stdio -M virt > -cpu cortex-a15 -enable-kvm -kernel arm/boot.flat -smp 1 -append vectors > kvm [1257]: load/store instruction decoding not implemented > error: kvm run failed Function not implemented > ./arm-run: line 16: 1256 Aborted $command "$@" > Return value from qemu: 134 > FAIL boot_vectors > > I am using FastModels Model Debugger version 8.2.028, with a model of this > characteristics: > > Model: > ------ > Model name: ARM_Cortex-A15 > Instance: cluster.cpu0 > Using CADI 2.0 interface revision 0. > Version: 8.2.72 > Generated by Core Generator: No > Needs SimGen License: No So far I've only tested on real hardware. So this could be the difference. > > running the latest stable linux release and qemu-devel's latest qemu with > the patches indicated here > https://lists.gnu.org/archive/html/qemu-devel/2013-10/msg02428.html plus > > [1] http://lists.nongnu.org/archive/html/qemu-devel/2013-10/msg01815.html > > I tested the instalation by running a linux with the same setup using this call: > qemu-system-arm \ > -display none \ > -enable-kvm \ > -kernel zImage\ > -m 128 -M virt -cpu cortex-a15 \ > -drive if=none,file=linux.img,id=fs \ > -device virtio-blk-device,drive=fs > > As I said, the tests pass if the kvm is not enabled and fail otherwise. I > have added a few printfs for debugging and I can tell that the code in > boot.c runs ok, but then when virtio_testdev is called (from > virtio_testdev_exit) the execution throws an exception (more specifically > the line *tdp++ = cpu_to_le32(va_arg(va, unsigned)); inside the first while. Hmm, even more confusing, as this isn't the first mmio access. > > I am not used to sending emails to this kind of list, so I don't know if I > am being too specific, too little or maybe not even giving the right > information. Please tell me what else you need and if you can help me solve > this problem. Your details are good, but instead of just stating 'latest' for your kernel and qemu versions, please give the exact version numbers. I've been busy with other things lately, but I'm due to post a v2 of this series. I should be able to finish that off this week. When I do, I'll see if I can test it over FastModel as well this time. Thanks for starting to poke at this! drew -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
