From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/5] arm64: Signal context expansion
Date: Fri, 9 Sep 2016 15:15:41 +0100 [thread overview]
Message-ID: <1473430576-20792-1-git-send-email-Dave.Martin@arm.com> (raw)
In preparation for supporting the ARM Scalable Vector Extension in the
Linux kernel, it is necessary to be able to save more data in the signal
frame than can be accommodated in the existing arm64 signal frame
structure.
To minimise ABI impact the current structures are retained as-is, and a
new extra_context record is defined, which (if present) declares some
additional space beyond the standard arm64 signal frame.
This new record can be added in sigframe.__reserved[] if there is a
need to allocate extra space beyond the standard signal frame. The
extra block of memory referenced by extra_context can then be parsed in
the same way as sigcontext.__reserved[]. Old code should just ignore
the whole thing as an unrecognised record. To maintain backward
compatibility, signal context records defined today are always placed
directly in __reserved[], never in the block referenced by
extra_context.
This series also does some refactoring in order to make it easier to add
records to the signal frame in the future, using the new expansion
mechanism. The extra_context mechanism is hidden behind a simple
allocator that grows and signal frame only as needed.
Note: this series makes rt_sigreturn somewhat stricter about parsing the
signal frame than previously: violators will be SEGV'd. This should
only be an ABI break for software that was doing something wrong in the
first place, but I'm open to suggestions if people have concerns about
it.
Dave Martin (5):
arm64: signal: Refactor sigcontext parsing in rt_sigreturn
arm64: signal: factor frame layout and population into separate passes
arm64: signal: factor out signal frame record allocation
arm64: signal: Allocate extra sigcontext space as needed
arm64: signal: Parse extra_context during sigreturn
arch/arm64/include/uapi/asm/sigcontext.h | 27 +++
arch/arm64/kernel/signal.c | 355 ++++++++++++++++++++++++++++---
2 files changed, 350 insertions(+), 32 deletions(-)
--
2.1.4
next reply other threads:[~2016-09-09 14:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 14:15 Dave Martin [this message]
2016-09-09 14:15 ` [RFC PATCH 1/5] arm64: signal: Refactor sigcontext parsing in rt_sigreturn Dave Martin
2016-09-09 14:15 ` [RFC PATCH 2/5] arm64: signal: factor frame layout and population into separate passes Dave Martin
2016-09-09 14:15 ` [RFC PATCH 3/5] arm64: signal: factor out signal frame record allocation Dave Martin
2016-09-09 14:15 ` [RFC PATCH 4/5] arm64: signal: Allocate extra sigcontext space as needed Dave Martin
2016-09-09 14:15 ` [RFC PATCH 5/5] arm64: signal: Parse extra_context during sigreturn Dave Martin
2016-09-09 14:39 ` [RFC PATCH 0/5] arm64: Signal context expansion Florian Weimer
2016-09-09 15:21 ` Dave Martin
2016-09-09 17:01 ` Florian Weimer
2016-09-12 11:17 ` Dave Martin
2016-09-12 12:49 ` Florian Weimer
2016-09-12 15:21 ` Dave Martin
2016-09-12 15:01 ` Szabolcs Nagy
2016-09-12 15:30 ` Dave Martin
2016-09-12 16:44 ` Szabolcs Nagy
2016-09-12 17:24 ` Dave Martin
2016-09-13 9:28 ` Florian Weimer
2016-09-13 15:52 ` Dave Martin
2016-09-13 16:02 ` Florian Weimer
2016-09-15 16:45 ` Dave Martin
2016-09-16 12:10 ` Florian Weimer
2016-09-16 17:39 ` 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=1473430576-20792-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).