From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, broonie@kernel.org,
catalin.marinas@arm.com, james.morse@arm.com,
kaleshsingh@google.com, madvenka@linux.microsoft.com,
maz@kernel.org, tabba@google.com
Subject: Re: [PATCH v2 2/8] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record()
Date: Mon, 8 Aug 2022 12:46:25 +0100 [thread overview]
Message-ID: <YvD3kfVMUoEw6sSw@FVFF77S0Q05N> (raw)
In-Reply-To: <20220808113810.GA32107@willie-the-truck>
On Mon, Aug 08, 2022 at 12:38:10PM +0100, Will Deacon wrote:
> On Fri, Aug 05, 2022 at 01:45:16PM +0100, Mark Rutland wrote:
> > The unwind_next_common() function unwinds a single frame record. There
> > are other unwind steps (e.g. unwinding through trampolines) which are
> > handled in the regular kernel unwinder, and in future there may be other
> > common unwind helpers.
> >
> > Clarify the purpose of unwind_next_common() by renaming it to
> > unwind_next_frame_record(). At the same time, add commentary, and delete
> > the redundant comment at the top of asm/stacktrace/common.h.
> >
> > There should be no functional change as a result of this patch.
> >
> > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > Reviewed-by: Kalesh Singh <kaleshsingh@google.com>
> > Reviewed-by: Mark Brown <broonie@kernel.org>
> > Cc: Fuad Tabba <tabba@google.com>
> > Cc: Kalesh Singh <kaleshsingh@google.com>
> > Cc: Madhavan T. Venkataraman <madvenka@linux.microsoft.com>
> > Cc: Marc Zyngier <maz@kernel.org>
> > ---
> > arch/arm64/include/asm/stacktrace/common.h | 22 ++++++++++++----------
> > arch/arm64/kernel/stacktrace.c | 2 +-
> > arch/arm64/kvm/hyp/nvhe/stacktrace.c | 2 +-
> > arch/arm64/kvm/stacktrace.c | 4 ++--
> > 4 files changed, 16 insertions(+), 14 deletions(-)
> >
> > diff --git a/arch/arm64/include/asm/stacktrace/common.h b/arch/arm64/include/asm/stacktrace/common.h
> > index 01dc9f44a24a7..676002d7d333c 100644
> > --- a/arch/arm64/include/asm/stacktrace/common.h
> > +++ b/arch/arm64/include/asm/stacktrace/common.h
> > @@ -2,13 +2,6 @@
> > /*
> > * Common arm64 stack unwinder code.
> > *
> > - * To implement a new arm64 stack unwinder:
> > - * 1) Include this header
> > - *
> > - * 2) Call into unwind_next_common() from your top level unwind
> > - * function, passing it the validation and translation callbacks
> > - * (though the later can be NULL if no translation is required).
> > - *
> > * See: arch/arm64/kernel/stacktrace.c for the reference implementation.
> > *
> > * Copyright (C) 2012 ARM Ltd.
> > @@ -139,9 +132,18 @@ typedef bool (*on_accessible_stack_fn)(const struct task_struct *tsk,
> > unsigned long sp, unsigned long size,
> > struct stack_info *info);
> >
> > -static inline int unwind_next_common(struct unwind_state *state,
> > - on_accessible_stack_fn accessible,
> > - stack_trace_translate_fp_fn translate_fp)
> > +/*
> > + * unwind_next_frame_record() - Unwind to the next frame record indicated by
> > + * @state->fp.
> > + *
> > + * @state: the current unwind state.
> > + * @accessible: determines whether the frame record is accessible
> > + * @translate_fp: translates the fp prior to access (may be NULL)
> > + */
>
> This looks like kerneldoc, so you I think you should make the opening "/*" a
> "/**".
I agree; that's also true for all the other comments in this file.
Would you mind if I did that as a follow-up fixing all of them?
Otherwise, I can spin a v3 with a preparatory patch for the existing instances.
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-08 11:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 12:45 [PATCH v2 0/8] arm64: stacktrace: cleanups and improvements Mark Rutland
2022-08-05 12:45 ` [PATCH v2 1/8] arm64: stacktrace: simplify unwind_next_common() Mark Rutland
2022-08-05 12:45 ` [PATCH v2 2/8] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record() Mark Rutland
2022-08-08 11:38 ` Will Deacon
2022-08-08 11:46 ` Mark Rutland [this message]
2022-08-05 12:45 ` [PATCH v2 3/8] arm64: stacktrace: move SDEI stack helpers to stacktrace code Mark Rutland
2022-08-05 12:45 ` [PATCH v2 4/8] arm64: stacktrace: add stackinfo_on_stack() helper Mark Rutland
2022-08-05 12:45 ` [PATCH v2 5/8] arm64: stacktrace: rework stack boundary discovery Mark Rutland
2022-08-05 12:45 ` [PATCH v2 6/8] arm64: stacktrace: remove stack type from fp translator Mark Rutland
2022-08-08 11:55 ` Will Deacon
2022-08-08 12:08 ` Mark Rutland
2022-08-08 12:30 ` Mark Rutland
2022-08-08 11:56 ` Mark Brown
2022-08-05 12:45 ` [PATCH v2 7/8] arm64: stacktrace: track all stack boundaries explicitly Mark Rutland
2022-08-08 12:04 ` Mark Brown
2022-08-05 12:45 ` [PATCH v2 8/8] arm64: stacktrace: track hyp stacks in unwinder's address space Mark Rutland
2022-08-08 12:09 ` Mark Brown
2022-08-06 1:11 ` [PATCH v2 0/8] arm64: stacktrace: cleanups and improvements Madhavan T. Venkataraman
2022-08-08 11:59 ` Will Deacon
2022-08-08 12:11 ` Mark Rutland
2022-08-08 12:28 ` Will Deacon
2022-08-08 12:33 ` Mark Rutland
2022-08-08 12:38 ` Mark Brown
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=YvD3kfVMUoEw6sSw@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kaleshsingh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=madvenka@linux.microsoft.com \
--cc=maz@kernel.org \
--cc=tabba@google.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