Hi Mike, On 10/04/18 14:19, Mike Bazov wrote: > Greetings, > > I'm developing a product based on KVM/ARM, in which i need to modify > the code that is responsible for entering into guest mode(i.e. EL1?) > and i don't really want to recompile the kernel and flash it again as > part of my development. I need to run on baremetal(on the board > itself) when testing my code. Recompiling the kernel is par for the course. You're probably changing fundamental structures in the kernel, and KVM is not exactly independent of the rest of the code base. > Any plans for supporting this in the near future? or any other > suggestions on a less painful development process? There are no plans to support this in general. As James pointed out, KVM needs to directly map the kernel at EL2, and requires to be part of the kernel text (see how kern_hyp_va works with respect to the kernel mappings). We *could* make it modular if we only had VHE, but we want a single kernel image a lot more than we'll ever want a modular KVM. So built in it will stay for the foreseeable future. As for a more civilized development model, you have two alternatives: - Use a proper boot loader that will load the kernel from a file system, - Use kexec to boot from one kernel to another. I use both every day. Hope this helps, M. -- Jazz is not dead. It just smells funny... _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
