[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ze9hH5UzmnkFrTmB@x1>
Date: Mon, 11 Mar 2024 16:53:03 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Anne Macedo <retpolanne@...teo.net>
Cc: Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] perf lock contention: skip traceiter functions
On Mon, Mar 11, 2024 at 07:25:16PM +0000, Anne Macedo wrote:
> Anne Macedo <retpolanne@...teo.net> writes:
> > Namhyung Kim <namhyung@...nel.org> writes:
> >> I think it depends on the kernel version and configuration. I remember
> >> I saw a different symbol on old kernels. But it'd be hard to handle all
> >> the cases. Let's have a single trace text section in the struct machine
> >> and use __traceiter_contention_begin only. If it's not found you can
> >> fallback to trace_contention_begin.
> However, if we fallback to trace_contention_begin, we won't be able to
> filter out both __traceiter_contention_begin and trace_contention_begin
> at the same time.
I think for ARM we need to skip both, no? I.e. I agree with Anne.
- Arnaldo
Powered by blists - more mailing lists