From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm64: Changes to register and stack dumps
Date: Thu, 19 Oct 2017 16:55:30 +0100 [thread overview]
Message-ID: <1508428534-20694-1-git-send-email-will.deacon@arm.com> (raw)
Hi all,
This handful of patches makes some significant changes to how we print
register/stack dumps and brings us inline with recent changes to x86.
The main changes are that we no longer print out the 'Exception stack:'
section and PC/LR values are resolved to a symbol+offset format where
possible.
Feedback welcome.
Will
--->8
Mark Rutland (1):
arm64: consistently log ESR and page table
Will Deacon (3):
arm64: traps: Don't print stack or raw PC/LR values in backtraces
arm64: traps: Pretty-print pstate in register dumps
arm64: uapi: Remove PSR_Q_BIT
arch/arm64/include/uapi/asm/ptrace.h | 1 -
arch/arm64/kernel/process.c | 24 ++++++++++---
arch/arm64/kernel/traps.c | 65 ++----------------------------------
arch/arm64/mm/fault.c | 7 ++--
4 files changed, 28 insertions(+), 69 deletions(-)
--
2.1.4
next reply other threads:[~2017-10-19 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 15:55 Will Deacon [this message]
2017-10-19 15:55 ` [PATCH 1/4] arm64: consistently log ESR and page table Will Deacon
2017-10-19 15:55 ` [PATCH 2/4] arm64: traps: Don't print stack or raw PC/LR values in backtraces Will Deacon
2017-10-19 15:55 ` [PATCH 3/4] arm64: traps: Pretty-print pstate in register dumps Will Deacon
2017-10-19 16:17 ` Mark Rutland
2017-10-20 15:58 ` Will Deacon
2017-10-20 16:08 ` Mark Rutland
2017-10-19 15:55 ` [PATCH 4/4] arm64: uapi: Remove PSR_Q_BIT Will Deacon
2017-10-20 22:53 ` [PATCH 0/4] arm64: Changes to register and stack dumps Laura Abbott
2017-10-23 9:03 ` Will Deacon
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=1508428534-20694-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@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).