[PATCH v2 2/5] KVM: arm64: Get rid of host SVE tracking/saving

Mark Brown broonie at kernel.org
Tue Nov 23 04:33:20 PST 2021


On Tue, Nov 23, 2021 at 10:11:33AM +0000, Marc Zyngier wrote:
> Mark Brown <broonie at kernel.org> wrote:

> > We don't need to change the ABI, the ABI just says we zero the registers
> > that aren't shared with FPSIMD.  Instead of doing that on taking a SVE
> > access trap to reenable SVE after having disabled TIF_SVE we could do

> That's not the point I'm trying to make.

> Userspace expects to have lost SVE information over a syscall (even if
> the VL is 128, it expects to have lost P0..P15 and FFR). How do you
> plan to tell userspace that this behaviour has changed?

My point is that this doesn't need to change.  Userspace can't tell if
we zeroed the non-shared state on syscall or on some later access trap.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20211123/12c8ede6/attachment.sig>


More information about the linux-arm-kernel mailing list