From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: Report signal frame size to userspace via auxv
Date: Tue, 8 May 2018 11:43:29 +0100 [thread overview]
Message-ID: <1525776211-28169-1-git-send-email-Dave.Martin@arm.com> (raw)
Because SVE makes the arm64 signal frame size variable, userspace will
ultimately need a way to detect the size.
This series adds support for exposing this information via a new auxv
entry AT_MINSIGSTKSZ.
These patches are taken from [1], with minor updates. (They were RFC
in that series, but there has been no significant discussion or
objections raised in the meantime, and no change in the understanding
of the problem being addressed here. I'd like to get discussions for
binding this to glibc started.)
Changes since [1]:
* Cache the value computed to AT_MINSIGSTKSZ so that the effort of
computing it does not need to be repeated on every exec.
[1] [PATCH v5 00/30] ARM Scalable Vector Extension (SVE)
lists.infradead.org/pipermail/linux-arm-kernel/2017-October/539993.html
Dave Martin (2):
arm64: signal: Report signal frame size to userspace via auxv
arm64/sve: signal: Include SVE when computing AT_MINSIGSTKSZ
arch/arm64/include/asm/elf.h | 5 +++
arch/arm64/include/asm/processor.h | 3 ++
arch/arm64/include/uapi/asm/auxvec.h | 3 +-
arch/arm64/kernel/signal.c | 68 ++++++++++++++++++++++++++++++++----
4 files changed, 71 insertions(+), 8 deletions(-)
--
2.1.4
next reply other threads:[~2018-05-08 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 10:43 Dave Martin [this message]
2018-05-08 10:43 ` [PATCH 1/2] arm64: signal: Report signal frame size to userspace via auxv Dave Martin
2018-05-08 11:30 ` Mark Rutland
2018-05-08 11:43 ` Dave Martin
2018-05-08 12:26 ` Mark Rutland
2018-05-08 12:29 ` Dave Martin
2018-05-08 10:43 ` [PATCH 2/2] arm64/sve: signal: Include SVE when computing AT_MINSIGSTKSZ Dave Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1525776211-28169-1-git-send-email-Dave.Martin@arm.com \
--to=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).