From mboxrd@z Thu Jan 1 00:00:00 1970 From: fweimer@redhat.com (Florian Weimer) Date: Tue, 13 Sep 2016 18:02:45 +0200 Subject: [RFC PATCH 0/5] arm64: Signal context expansion In-Reply-To: <20160913155151.GA1574@e103592.cambridge.arm.com> References: <1473430576-20792-1-git-send-email-Dave.Martin@arm.com> <20160909152047.GA3958@e103592.cambridge.arm.com> <20160912111749.GB3958@e103592.cambridge.arm.com> <57D6C33D.9020003@arm.com> <20160912153015.GD3958@e103592.cambridge.arm.com> <9969568a-f969-d904-52b3-14f80c3abec4@redhat.com> <20160913155151.GA1574@e103592.cambridge.arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 09/13/2016 05:52 PM, Dave Martin wrote: > Agreed. I'll need to think some more about how this should work in > general. Thanks. Depending on some SVE implementations details (which I know nothing about, I only saw some public overview slides), we may also need additional storage space to preserve SVE registers in the dynamic linker. Due to lazy binding, this code cn be called from a signal handler, so this needs to be factored into stack size requirements as well. Problematic are register width extensions used for argument passing and callee-saved registers whose width has been extended. Both are particularly challenging to deal with if existing vector instructions clear the extension part (which may be desirable for other reasons). The size of the jmp_buf type is a concern as well. Florian