Thread (112 messages) flat view 112 messages, 12 authors, 11d ago

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

From: Kohei Enju <hidden>
Date: 2026-09-07 11:13:01
Also in: kvm, kvmarm, linux-coco, lkml

Hi Marc,

On 09/07 11:10, Marc Zyngier wrote:
On Mon, 07 Sep 2026 06:05:29 +0100,
Kohei Enju [off-list ref] wrote:

[...]
quoted
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.
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help