From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Ingo Molnar <mingo@kernel.org>, Jiri Slaby <jirislaby@kernel.org>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Miroslav Benes <mbenes@suse.cz>
Subject: Re: [PATCH v2 0/3] arm64: Convert to ARCH_STACKWALK
Date: Tue, 1 Sep 2020 17:06:26 +0100 [thread overview]
Message-ID: <20200901160626.GE95447@C02TD0UTHF1T.local> (raw)
In-Reply-To: <20200819124913.37261-1-broonie@kernel.org>
Hi,
On Wed, Aug 19, 2020 at 01:49:10PM +0100, Mark Brown wrote:
> This series updates the arm64 stacktrace code to use the newer and much
> simpler arch_stack_walk() interface, the main benefit being a single
> entry point to the arch code with no need for the arch code to worry
> about skipping frames. Along the way I noticed that the reliable
> parameter to the arch_stack_walk() callback appears to be redundant
> so there's also a patch here removing that from the existing code to
> simplify the interface.
>
> This is preparatory work for implementing reliable stack trace for
> arm64.
This all looks pretty nice!
Just to check, has the skipping logic been tested to work equivalently
to what we had before? By inspection I think it should, but since it
relies on function call boundaries it always strikes me as fragile.
If you could confirm that (e.g. with LKDTM perhaps?) that'd be great.
Assuming that looks right, for the series:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
>
> v2: Rebase onto v5.9-rc1.
>
> Mark Brown (3):
> stacktrace: Remove reliable argument from arch_stack_walk() callback
> arm64: stacktrace: Make stack walk callback consistent with generic
> code
> arm64: stacktrace: Convert to ARCH_STACKWALK
>
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/stacktrace.h | 2 +-
> arch/arm64/kernel/perf_callchain.c | 6 +--
> arch/arm64/kernel/return_address.c | 8 +--
> arch/arm64/kernel/stacktrace.c | 84 ++++-------------------------
> arch/s390/kernel/stacktrace.c | 4 +-
> arch/x86/kernel/stacktrace.c | 10 ++--
> include/linux/stacktrace.h | 5 +-
> kernel/stacktrace.c | 8 ++-
> 9 files changed, 30 insertions(+), 98 deletions(-)
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-09-01 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 12:49 [PATCH v2 0/3] arm64: Convert to ARCH_STACKWALK Mark Brown
2020-08-19 12:49 ` [PATCH v2 1/3] stacktrace: Remove reliable argument from arch_stack_walk() callback Mark Brown
2020-09-02 9:26 ` Miroslav Benes
2020-08-19 12:49 ` [PATCH v2 2/3] arm64: stacktrace: Make stack walk callback consistent with generic code Mark Brown
2020-09-02 9:26 ` Miroslav Benes
2020-08-19 12:49 ` [PATCH v2 3/3] arm64: stacktrace: Convert to ARCH_STACKWALK Mark Brown
2020-09-02 9:32 ` Miroslav Benes
2020-09-02 18:50 ` Mark Rutland
2020-09-10 17:34 ` Mark Brown
2020-09-01 16:06 ` Mark Rutland [this message]
2020-09-02 17:38 ` [PATCH v2 0/3] arm64: " Mark Brown
2020-09-02 19:03 ` Mark Rutland
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=20200901160626.GE95447@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=borntraeger@de.ibm.com \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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