On Mon, 2024-03-18 at 16:57 +0000, Marc Zyngier wrote: > > > > > There *is* a way for a VMM to opt *out* of newer PSCI versions... by > > setting a per-vCPU "special" register that actually ends up setting the > > PSCI version KVM-wide. Quite why this isn't just a simple KVM_CAP, I > > have no idea. > > Because the expectations are that the VMM can blindly save/restore the > guest's state, including the PSCI version, and restore that blindly. > KVM CAPs are just a really bad design pattern for this sort of things. Hm, am I missing something here? Does the *guest* get to set the PSCI version somehow, and opt into the latest version that it understands regardless of what the firmware/host can support? Because if not, surely it's just part of the basic shape of the machine, like "how many vCPUs does it have". You don't need to be able to query it back again. I don't think we ever aspired to be able to hand an arbitrary KVM fd to a userspace VMM and have the VMM be able to drive that VM without having any a priori context, did we?
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
