Hi all, I recently presented some slides [1] at Plumbers about the challenge of growing the signal frame, and why we need to grow it on arm64 and (seemingly) other architectures. I didn't get any controversial feedback there, but this topic is relevant to linux-api too. Does anyone have a view on the AT_MINSIGSTKSZ and ucontext proposals outlined in the slides? SVE itself requires a fair number of arm64-specific ABI additions -- there's a documentation patch [3] outlining everything. (The patches are not merged yet, but see [2] for the most recent version of the series.) If anyone has any comments on the design, I'd like to hear them. Thanks ---Dave [1] Growing CPU register state without breaking ABI (much) https://linuxplumbersconf.org/2017/ocw//system/presentations/4671/original/plumbers-dm-2017.pdf [2] [PATCH v2 00/28] ARM Scalable Vector Extension (SVE) http://lists.infradead.org/pipermail/linux-arm-kernel/2017-August/529575.html [3] [PATCH v2 26/28] arm64/sve: Add documentation http://lists.infradead.org/pipermail/linux-arm-kernel/2017-August/529595.html -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
