[PATCH v16 22/45] KVM: arm64: CCA: Handle RMI_EXIT_RIPAS_CHANGE

Kohei Enju enju.kohei at fujitsu.com
Mon Sep 7 04:12:36 PDT 2026


Hi Marc,

On 09/07 11:10, Marc Zyngier wrote:
> On Mon, 07 Sep 2026 06:05:29 +0100,
> Kohei Enju <enju.kohei at fujitsu.com> wrote:
> 
> [...]
> 
> > Although the root cause is an RMM bug, should we also guard RIPAS_SET
> > against this no-progress case?
> 
> No. We really should *prevent* the kernel from using a known broken
> RMM. 

I understand.

> Which brings me to one of my long standing request: how to we
> enforce the minimum version of RMM that KVM is willing to work with?
> 
> We absolutely need to have a hard deprecation mechanism in place
> before day-1.

Agreed. Such a mechanism is clearly necessary.

Is there any ongoing work to address this that you are aware of? This
seems like a fairly broad topic that may require a separate discussion.

Thanks,
Kohei

> 
> 	M.
> 
> -- 
> Without deviation from the norm, progress is not possible.



More information about the linux-arm-kernel mailing list