From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: Provide ESR_EL1 information to user signal handlers
Date: Sun, 6 Apr 2014 23:19:03 +0100 [thread overview]
Message-ID: <1396822746-26241-1-git-send-email-catalin.marinas@arm.com> (raw)
The arm64 port omitted the fault status information in sigcontext.
However, there are emulators like Qemu that rely on such information to
distinguish between a read or a write fault without decoding the
faulting instruction.
The first patch fixes the compat case. The second patch is a clean-up
and the third introduces the esr_context structure with its own magic to
be stored on the signal handler stack when applicable (SIGSEGV and
SIGBUS). Given that this hardware register is meant for EL1 consumption,
if significant changes are made in future architecture versions a new
magic number will be introduced.
Catalin Marinas (3):
arm64: Provide read/write fault information in compat signal handlers
arm64: Remove the aux_context structure
arm64: Expose ESR_EL1 information to user when SIGSEGV/SIGBUS
arch/arm64/include/asm/processor.h | 1 +
arch/arm64/include/asm/sigcontext.h | 31 --------------------------
arch/arm64/include/uapi/asm/sigcontext.h | 7 ++++++
arch/arm64/kernel/signal.c | 37 +++++++++++++++++++++++---------
arch/arm64/kernel/signal32.c | 4 +++-
arch/arm64/kernel/traps.c | 7 ++++--
arch/arm64/mm/fault.c | 3 ++-
7 files changed, 45 insertions(+), 45 deletions(-)
delete mode 100644 arch/arm64/include/asm/sigcontext.h
next reply other threads:[~2014-04-06 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 22:19 Catalin Marinas [this message]
2014-04-06 22:19 ` [PATCH 1/3] arm64: Provide read/write fault information in compat signal handlers Catalin Marinas
2014-04-07 9:39 ` Michal Simek
2014-04-07 11:41 ` Catalin Marinas
2014-04-06 22:19 ` [PATCH 2/3] arm64: Remove the aux_context structure Catalin Marinas
2014-04-06 22:19 ` [PATCH 3/3] arm64: Expose ESR_EL1 information to user when SIGSEGV/SIGBUS Catalin Marinas
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=1396822746-26241-1-git-send-email-catalin.marinas@arm.com \
--to=catalin.marinas@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).