On Sun, 25 Aug 2024 18:09:48 +0100, "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx> wrote: > > On Sun, Aug 25, 2024 at 05:46:36PM +0100, Marc Zyngier wrote: > > On Tue, 23 Jul 2024 08:19:59 +0100, > > Shaoqin Huang <shahuang@xxxxxxxxxx> wrote: > > > > > > Hi guys, > > > > > > This is another try to allow userspace to change ID_AA64PFR1_EL1, and we want to > > > give userspace the ability to control the visible feature set for a VM, which > > > could be used by userspace in such a way to transparently migrate VMs. > > > > > > I think this looks OK now, thanks for going through the motions and > > doing the right thing. > > > > What is missing is similar handling for 32bit ID registers, but I'm > > not sure we keen on going down that road -- machines capable of > > running those are on their way out. This can be done later anyway, > > should anyone care. > > The Aarch32 ID registers need doing - we've already established that > fact. Sadly, you decided you wouldn't respond to my patch addressing > one of the Aarch32 ID registers despite me sending follow-ups to nicely > ask you about this - you seemed to go utterly silent on it. No, Russell. *you* went utterly silent after your May patch. You sent an RFC, to which people responded. Given that your last email on the subject was almost 4 months ago and that you never brought the subject up again, it can't be that big a deal. To me, an RFC means "I have this idea, and I'm not sure how to do it". An RFC is usually only a proof of concept that has no purpose being taken at face value. If you want a patch taken seriously, don't send it as an RFC. And send it again if nobody replies. It's not that this is anything new. > The Aarch32 ID registers have changed value between different kernel > versions, and given that QEMU saves and restores _all_ ID registers, > changes to these ID registers cause a regression if one attempts to > migrate VMs between one kernel version and the next. It doesn't even > have to be between two physical machines. Libvirt supports managed- > saving on reboot, where it saves an image of a VM at shutdown, and > restores it at the next reboot. These changes in ID registers render > effectively data loss in VMs that have been managed-saved - the > saved state of the VM has to either be destroyed, or the host kernel > reverted back and _never_ moved forward. > > As you don't seem to be keen to address this (by ignoring my emails > on the topic, and now suggesting in your response above that you're > not keen to do anything with the Aarch32 ID registers, I guess this > just means that KVM on Aarch64 is going to forever suck. I'm fine with that. Nobody is forced to use it, and I don't feel the need to put extra effort on things I don't care about any more. AArch32 support is one of these things, amongst many others. If you want the support to improve, I suggest you send patches. And send them again if no reply shows up in a timely manner. Because you're probably the last person who gives a damn about the AArch32 support in KVM. And if not even you can be bothered to fix it, then support for AArch32 EL1 should probably be removed altogether (I'm all for deleting unused code). > I'm sure Oliver will recall my emails on this which you've decided to > ignore... he was supportive of my efforts to address this. I'm supportive as well. I'm just not going to fix it for you. M. -- Without deviation from the norm, progress is not possible.
