[PATCH] arm64: signal: Update sigcontext reservations table

Mark Brown broonie at kernel.org
Wed Jul 31 09:14:46 PDT 2024


On Wed, Jul 31, 2024 at 05:09:36PM +0100, Dave Martin wrote:
> On Wed, Jul 31, 2024 at 03:58:00PM +0100, Mark Brown wrote:

> > + * where vl is the non-streaming SVE vector length, as set with PR_SVE_SET_VL,
> > + * and svl is the streaming SVE vector length, as set with PR_SME_SET_VL.

> > I'd just say VL is the vector length, that's the term the architecture
> > uses and it says it's set with PR_SVE_SET_VL to clarify.

> It's the worst-case sigframe size that we care about here, regardless
> of what code a signal is delivered in the middle of.  Surely that
> depends on both vector length settings?

Sure - what I'm saying is that you should refer to the non-streaming
vector length as just the vector length in line with the architecture
terminology.  The architecture does refer to the streaming vector length
as the streaming SVE vector length sometimes so I guess we can stick
with that there.

> Can you think of a description that clarifies this?

s/non-streaming SVE vector length/vector length/
-------------- 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/20240731/dc40e6a8/attachment.sig>


More information about the linux-arm-kernel mailing list