From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: broonie@kernel.org, catalin.marinas@arm.com,
kaleshsingh@google.com, madvenka@linux.microsoft.com,
mark.rutland@arm.com, will@kernel.org
Subject: [PATCH 0/6] arm64: stacktrace cleanups
Date: Wed, 13 Apr 2022 15:59:04 +0100 [thread overview]
Message-ID: <20220413145910.3060139-1-mark.rutland@arm.com> (raw)
This series is a collection of cleanup / refactoring changes for the
arm64 stacktrace code.
There should be no functional change as a result of this series; the
bulk of the series is a rename for consistency with the core+x86 unwind
code, and the only structural changes are the removal of a redundant
NULL check and making some code private to
arch/arm64/kernel/stacktrace.c.
The bulk of the series has been extracted from v13 of Madhavan's series
adding reliability checks:
https://lore.kernel.org/linux-arm-kernel/20220117145608.6781-1-madvenka@linux.microsoft.com/
... and I've rebased the extracted patches atop v5.18-rc1. The rest of
that series needs further review, and I'd like to get the
uncontroversial bits out of the way now while that continues so that we
can make other changes in this area.
The couple of patches from me are new as of this posting, but I'm hoping
those are simple enough that this can be picked up as-is.
The series can be found in my arm64/stacktrace/cleanups branch:
https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=arm64/stacktrace/cleanups
git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/stacktrace/cleanups
Thanks,
Mark.
Madhavan T. Venkataraman (4):
arm64: stacktrace: remove NULL task check from unwind_frame()
arm64: stacktrace: rename unwinder functions
arm64: stacktrace: rename stackframe to unwind_state
arm64: stacktrace: align with common naming
Mark Rutland (2):
arm64: stacktrace: delete PCS comment
arm64: stacktrace: make struct stackframe private to stacktrace.c
arch/arm64/include/asm/stacktrace.h | 32 -------
arch/arm64/kernel/stacktrace.c | 124 ++++++++++++++++------------
2 files changed, 69 insertions(+), 87 deletions(-)
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-13 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 14:59 Mark Rutland [this message]
2022-04-13 14:59 ` [PATCH 1/6] arm64: stacktrace: remove NULL task check from unwind_frame() Mark Rutland
2022-04-13 14:59 ` [PATCH 2/6] arm64: stacktrace: delete PCS comment Mark Rutland
2022-04-13 15:02 ` Madhavan T. Venkataraman
2022-04-13 15:59 ` Mark Brown
2022-04-13 16:11 ` Mark Rutland
2022-04-13 14:59 ` [PATCH 3/6] arm64: stacktrace: make struct stackframe private to stacktrace.c Mark Rutland
2022-04-13 15:03 ` Madhavan T. Venkataraman
2022-04-13 15:59 ` Mark Brown
2022-04-13 14:59 ` [PATCH 4/6] arm64: stacktrace: rename unwinder functions Mark Rutland
2022-04-13 14:59 ` [PATCH 5/6] arm64: stacktrace: rename stackframe to unwind_state Mark Rutland
2022-04-13 14:59 ` [PATCH 6/6] arm64: stacktrace: align with common naming Mark Rutland
2022-04-13 16:00 ` Mark Brown
2022-04-19 17:10 ` [PATCH 0/6] arm64: stacktrace cleanups Kalesh Singh
2022-04-22 18:27 ` 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=20220413145910.3060139-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kaleshsingh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=madvenka@linux.microsoft.com \
--cc=will@kernel.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).