linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>
To: Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: broonie@kernel.org, catalin.marinas@arm.com, james.morse@arm.com,
	kaleshsingh@google.com, maz@kernel.org, tabba@google.com,
	will@kernel.org
Subject: Re: [PATCH v3 1/9] arm64: stacktrace: fix kerneldoc comments
Date: Tue, 23 Aug 2022 00:11:10 -0500	[thread overview]
Message-ID: <d7122ed2-358e-2a79-ebaa-9ed37616ef6f@linux.microsoft.com> (raw)
In-Reply-To: <20220815113922.3280255-2-mark.rutland@arm.com>

Reviewed-by: Madhavan T. Venkataraman <madvenka@linux.microsoft.com>

On 8/15/22 06:39, Mark Rutland wrote:
> Many of the comment blocks in the arm64 stacktrace code are *almost*
> kerneldoc, but not quite.
> 
> Convert them to kerneldoc, as was presumably originally intended.
> 
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> 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>
> Cc: Mark Brown <broonie@kernel.org>
> ---
>  arch/arm64/include/asm/stacktrace/common.h | 28 +++++++++++++---------
>  arch/arm64/include/asm/stacktrace/nvhe.h   |  4 ++--
>  2 files changed, 19 insertions(+), 13 deletions(-)
> 
> diff --git a/arch/arm64/include/asm/stacktrace/common.h b/arch/arm64/include/asm/stacktrace/common.h
> index f58eb944c46fb..b8b20ef5aa5db 100644
> --- a/arch/arm64/include/asm/stacktrace/common.h
> +++ b/arch/arm64/include/asm/stacktrace/common.h
> @@ -38,9 +38,8 @@ struct stack_info {
>  	enum stack_type type;
>  };
>  
> -/*
> - * A snapshot of a frame record or fp/lr register values, along with some
> - * accounting information necessary for robust unwinding.
> +/**
> + * struct unwind_state - state used for robust unwinding.
>   *
>   * @fp:          The fp value in the frame record (or the real fp)
>   * @pc:          The lr value in the frame record (or the real lr)
> @@ -113,27 +112,34 @@ static inline void unwind_init_common(struct unwind_state *state,
>  	state->prev_type = STACK_TYPE_UNKNOWN;
>  }
>  
> -/*
> - * stack_trace_translate_fp_fn() - Translates a non-kernel frame pointer to
> - * a kernel address.
> +/**
> + * typedef stack_trace_translate_fp_fn() - Translates a non-kernel frame
> + * pointer to a kernel address.
>   *
>   * @fp:   the frame pointer to be updated to its kernel address.
>   * @type: the stack type associated with frame pointer @fp
>   *
> - * Returns true and success and @fp is updated to the corresponding
> - * kernel virtual address; otherwise returns false.
> + * Return: true if the VA can be translated, false otherwise.
> + *
> + * Upon success @fp is updated to the corresponding kernel virtual address.
>   */
>  typedef bool (*stack_trace_translate_fp_fn)(unsigned long *fp,
>  					    enum stack_type type);
>  
> -/*
> - * on_accessible_stack_fn() - Check whether a stack range is on any
> - * of the possible stacks.
> +/**
> + * typedef on_accessible_stack_fn() - Check whether a stack range is on any of
> + * the possible stacks.
>   *
>   * @tsk:  task whose stack is being unwound
>   * @sp:   stack address being checked
>   * @size: size of the stack range being checked
>   * @info: stack unwinding context
> + *
> + * Return: true if the stack range is accessible, false otherwise.
> + *
> + * Upon success @info is updated with information for the relevant stack.
> + *
> + * Upon failure @info is updated with the UNKNOWN stack.
>   */
>  typedef bool (*on_accessible_stack_fn)(const struct task_struct *tsk,
>  				       unsigned long sp, unsigned long size,
> diff --git a/arch/arm64/include/asm/stacktrace/nvhe.h b/arch/arm64/include/asm/stacktrace/nvhe.h
> index d5527b6003908..25ab83a315a76 100644
> --- a/arch/arm64/include/asm/stacktrace/nvhe.h
> +++ b/arch/arm64/include/asm/stacktrace/nvhe.h
> @@ -20,8 +20,8 @@
>  
>  #include <asm/stacktrace/common.h>
>  
> -/*
> - * kvm_nvhe_unwind_init - Start an unwind from the given nVHE HYP fp and pc
> +/**
> + * kvm_nvhe_unwind_init() - Start an unwind from the given nVHE HYP fp and pc
>   *
>   * @state : unwind_state to initialize
>   * @fp    : frame pointer at which to start the unwinding.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-08-23  5:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 11:39 [PATCH v3 0/9] arm64: stacktrace: cleanups and improvements Mark Rutland
2022-08-15 11:39 ` [PATCH v3 1/9] arm64: stacktrace: fix kerneldoc comments Mark Rutland
2022-08-16 15:59   ` Mark Brown
2022-08-23  5:11   ` Madhavan T. Venkataraman [this message]
2022-08-15 11:39 ` [PATCH v3 2/9] arm64: stacktrace: simplify unwind_next_common() Mark Rutland
2022-08-15 11:39 ` [PATCH v3 3/9] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record() Mark Rutland
2022-08-15 11:39 ` [PATCH v3 4/9] arm64: stacktrace: move SDEI stack helpers to stacktrace code Mark Rutland
2022-08-15 11:39 ` [PATCH v3 5/9] arm64: stacktrace: add stackinfo_on_stack() helper Mark Rutland
2022-08-15 11:39 ` [PATCH v3 6/9] arm64: stacktrace: rework stack boundary discovery Mark Rutland
2022-08-15 11:39 ` [PATCH v3 7/9] arm64: stacktrace: remove stack type from fp translator Mark Rutland
2022-08-15 11:39 ` [PATCH v3 8/9] arm64: stacktrace: track all stack boundaries explicitly Mark Rutland
2022-08-15 11:39 ` [PATCH v3 9/9] arm64: stacktrace: track hyp stacks in unwinder's address space 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=d7122ed2-358e-2a79-ebaa-9ed37616ef6f@linux.microsoft.com \
    --to=madvenka@linux.microsoft.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=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).