On 16/11/15 14:27, Mark Rutland wrote: > On Mon, Nov 16, 2015 at 01:11:55PM +0000, Marc Zyngier wrote: >> In order to run C code in HYP, we must make sure that the kernel's >> RO section in mapped into HYP (otherwise things break badly). > > Somewhat tangential, but do we have any strong guarantees that the hyp > text is otherwise safe in its address space which differs from that of > the kernel proper? > > i.e. do we need something like we did for the EFI stub in commit > e8f3010f7326c003 ("arm64/efi: isolate EFI stub from the kernel proper")?
Probably. That will make things more difficult for VHE, where there are function calls between the kernel and the "hypervisor" (kvm_call_hyp() and panic() are the most obvious ones). I'll have a look, thanks for the pointer. M. -- Jazz is not dead. It just smells funny... _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm