On Mon, Jul 15, 2019 at 02:48:49PM +0100, Mark Rutland wrote: > On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote: [...] > > So long as KVM_EXIT_HYPERCALL reports sufficient information so that > > userspace can identify the cause as an SMC and retrieve the SMC > > immediate field, this seems feasible. > > > > For its own SMCCC APIs, KVM exclusively uses HVC, so rerouting SMC to > > userspace shouldn't conflict. > > Be _very_ careful here! In systems without EL3 (and without NV), SMC > UNDEFs rather than trapping to EL2. Given that, we shouldn't build a > hypervisor ABI that depends on SMC. Good point. I was hoping that was all ancient history by now, but if not... [...] Cheers ---Dave _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
