Linux Trace Kernel
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fgraph: Remove unused FGRAPH_MAX_INDEX
Date: Sun, 6 Sep 2026 11:22:42 +0900	[thread overview]
Message-ID: <20260906112242.421681769499f9f590d8c61d@kernel.org> (raw)
In-Reply-To: <20260905211922.1196366-1-donggeunyoo.kernel@gmail.com>

On Sun,  6 Sep 2026 06:19:22 +0900
Donggeun Yoo <donggeunyoo.kernel@gmail.com> wrote:

> FGRAPH_MAX_INDEX has no user, and it expands to FGRAPH_INDEX_SIZE and
> FGRAPH_RET_INDEX, neither of which is defined anywhere in the tree. It
> was added in that form by commit 91c46b0aa917 ("function_graph:
> Implement fgraph_reserve_data() and fgraph_retrieve_data()"), which
> introduced the current data word layout under new names, so anything
> referencing it would have failed to build ever since.
> 
> Remove it.
>

Looks good to me.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Thanks!
 
> Signed-off-by: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
> ---
> Found while reading the shadow stack word layout. The macro is dead in
> both senses: nothing references it, and it could not be used as it is.
> 
> Compile-tested only, with CONFIG_FUNCTION_GRAPH_TRACER=y and
> CONFIG_DYNAMIC_FTRACE=y. Removing an unreferenced macro cannot change
> generated code, so there is nothing to test at run time.
> 
>  kernel/trace/fgraph.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/kernel/trace/fgraph.c b/kernel/trace/fgraph.c
> index 40d373d65f9b..ed455b53513b 100644
> --- a/kernel/trace/fgraph.c
> +++ b/kernel/trace/fgraph.c
> @@ -143,9 +143,6 @@ enum {
>  #define FGRAPH_DATA_INDEX_MASK	GENMASK(FGRAPH_DATA_INDEX_BITS - 1, 0)
>  #define FGRAPH_DATA_INDEX_SHIFT	(FGRAPH_DATA_SHIFT + FGRAPH_DATA_BITS)
>  
> -#define FGRAPH_MAX_INDEX	\
> -	((FGRAPH_INDEX_SIZE << FGRAPH_DATA_BITS) + FGRAPH_RET_INDEX)
> -
>  #define FGRAPH_ARRAY_SIZE	FGRAPH_INDEX_BITS
>  
>  /*
> -- 
> 2.53.0
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2026-09-06  2:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 21:19 [PATCH] fgraph: Remove unused FGRAPH_MAX_INDEX Donggeun Yoo
2026-09-06  2:22 ` Masami Hiramatsu [this message]

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=20260906112242.421681769499f9f590d8c61d@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=donggeunyoo.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.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