[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176271786886.1711746.4583976812483575494.b4-ty@kernel.org>
Date: Sun, 09 Nov 2025 11:51:08 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Gabriel Marin <gmx@...gle.com>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Athira Rajeev <atrajeev@...ux.ibm.com>,
Gautam Menghani <gautam@...ux.ibm.com>, tanze <tanze@...inos.cn>,
Andi Kleen <ak@...ux.intel.com>, James Clark <james.clark@...aro.org>,
Zhongqiu Han <quic_zhonhan@...cinc.com>,
Yicong Yang <yangyicong@...ilicon.com>, Blake Jones <blakejones@...gle.com>,
Anubhav Shelat <ashelat@...hat.com>, Leo Yan <leo.yan@....com>,
Chun-Tse Shao <ctshao@...gle.com>, Thomas Falcon <thomas.falcon@...el.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v2 1/2] perf tool: Add the perf_tool argument to all
callbacks
On Fri, 07 Nov 2025 09:07:11 -0800, Ian Rogers wrote:
> Getting context for what a tool is doing, such as the perf_inject
> instance, using container_of the tool is a common pattern in the
> code. This isn't possible event_op2, event_op3 and event_op4 callbacks
> as the tool isn't passed. Add the argument and then fix function
> signatures to match. As tools maybe reading a tool from somewhere
> else, change that code to use the passed in tool.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists