Hi Andrew, On Thu, Aug 3, 2017 at 1:41 PM, Andrew Jones <drjones@xxxxxxxxxx> wrote: > (I trimmed the long CC list) > > On Fri, Jul 28, 2017 at 05:45:01PM -0400, Jintack Lim wrote: >> On Fri, Jul 28, 2017 at 4:13 PM, Bandan Das <bsd@xxxxxxxxxx> wrote: >> > Jintack Lim <jintack.lim@xxxxxxxxxx> writes: >> > ... >> >>> >> >>> I'll share my experiment setup shortly. >> >> >> >> I summarized my experiment setup here. >> >> >> >> https://github.com/columbia/nesting-pub/wiki/Nested-virtualization-on-ARM-setup >> > >> > Thanks Jintack! I was able to test L2 boot up with these instructions. >> >> Thanks for the confirmation! >> >> > >> > Next, I will try to run some simple tests. Any suggestions on reducing the L2 bootup >> > time in my test setup ? I think I will try to make the L2 kernel print >> > less messages; and maybe just get rid of some of the userspace services. >> > I also applied the patch to reduce the timer frequency btw. >> >> I think you can try to use those kernel parameters: "loglevel=1", with >> which the kernel print (almost) nothing during the boot process but >> the init process will print something, or "console=none", with which >> you don't see anything but the login message. I didn't used them >> because I wanted to see the L2 boot message as soon as possible :) >> > > For some quick testing, kvm-unit-tests can be used as an L2 guest. Just > copy the repository with compiled unit tests to the L1 disk image and > then run > > $ ./run_tests.sh Right. I used to run kvm-unit-tests in L1. I will mention that in the next cover letter. Thanks! > > Also, I've just added some support to it, available on this branch > > https://github.com/rhdrjones/kvm-unit-tests/commits/arm64/hyp-mode > > that may make it somewhat useful for L1 guest testing too. I've only > tested on TCG (which supports starting CPUs in EL2 by setting the virt > model's virtualization property) > > To use it for L1 guest testing, copy the repository with compiled unit > tests to the L0 disk image and run > > $ QEMU=/path/to/nested-qemu ./run_tests -- -cpu host,nested=true > > I've also added tests that are specifically for L1 guest testing. Below > is the output of running them on TCG > > $ ./run_tests.sh -g hyp -- -machine virtualization=on > PASS hyp (4 tests) > $ cat logs/hyp.log > timeout -k 1s --foreground 90s /home/drjones/code/rhdrjones/build/q/aarch64-softmmu/qemu-system-aarch64 -nodefaults -machine virt,accel=tcg -cpu cortex-a57 -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/hyp.flat -smp 4 -machine virtualization=on # -initrd /tmp/tmp.hDF1mV9Ck8 > INFO: hyp: NR_CPUS=4 > PASS: hyp: started EL2 > PASS: hyp: el2: hvc > PASS: hyp: eret to EL1 > PASS: hyp: el1: hvc > PASS: hyp: reset: started EL2 > PASS: hyp: reset: el2: hvc > PASS: hyp: reset: eret to EL1 > PASS: hyp: reset: el1: hvc > SUMMARY: 4 tests > > s/-machine virtualization=on/-cpu host,nested=true/ for the FastModel > environment. Maybe it'll work... This is cool! I'll test it in my environment! Thanks, Jintack > > Thanks, > drew _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm