Re: [PATCH v19 03/14] KVM: arm64: Manage GCS access and registers for guests
Mark Brown <[email protected]>
| Newsgroups | org.kernel.vger.linux-doc,dev.linux.lists.kvmarm,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Aug 20, 2026 at 03:28:39PM +0100, Leonardo Bras wrote: > On Thu, Aug 20, 2026 at 03:07:14PM +0100, Mark Brown wrote: > > I think what would help here would be to move to generating more of the > > save/restore sequences rather than open coding them, we could have lists > > of registers and then use data about the feature dependencies that the > > architecture has (hopefully it's already in the MRS, I didn't check) to > > generate these optimised feature checks rather than having to open code > > them. Possibly even list features and generate some of the register > > lists, though that would need far more special case handling and it's > > *much* less clear if there could be a benefit. > Yeah, that would automatize the feature dependency for register loading, > but maybe code would not be that clear on how it works? I have questionable > taste, though. I was thinking of generating as part of the build process rather than as a one off so you'd not actually look at the code in the normal course of affairs.
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmqHGwUACgkQJNaLcl1U h9ClIAf8C1PPh/jm0zRwE2TlZckmkQSd0+wAv9s16BA+buMf1y7Blt2cCUAx/+pm U3mobFvFSDF1COBWKajgd4TM0wmEbUYDYEd6bwxW38JUSWESaQNkEotcw/D+wCRG p16FUPjNexyrTzf1utNn/xnnDihxAxVkv5GaJtLvBISbIC+Sa+sw+PnIwTflkjYC CPJmsQEDCzRj+ibEU7rU6KTpUI7udB1A3s8uhnYVji5qsJlUZRVgyM4IbXTA37df n5ErCgi7ROl4Lzz53SFIvTdPwJntXuA96OSgfesk7LAJo+7Eq3KJggXX3OxSw6BS /F0eUbyIwjde7bxekGufQIE7j0rWnQ== =hyYp -----END PGP SIGNATURE-----