On 02/10/2015 09:28, Pavel Fedin wrote: > 2. Another possible approach, based on how device tree binding is handled by Linux. It is possible > to remove virtual timer IRQ from the device tree, in this case the kernel reverts to using physical > timer. When running under hypervisor, accesses to physical CP15 timer are trapped into HYP, > therefore we can forward them to userspace using new exit code, something like KVM_EXIT_REG_ACCESS. > In this case the timer would be also emulated by the userspace, which is slower, but allows better > emulation. Also, this could be used in order to run some other guests which just expect physical > timer to be there. > > Both approaches have their own limitations, but anyway this is much better than nothing. What do > you think, and which approach do you like more? I like the latter. But I guess one could even do both? Paolo _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
