[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a926f05d-03ec-4c78-83f2-3a50299e8be4@web.de>
Date: Sat, 8 Feb 2025 18:37:34 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Luo Gengkun <luogengkun@...weicloud.com>,
linux-perf-users@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>, Ian Rogers <irogers@...gle.com>,
Ingo Molnar <mingo@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
Kan Liang <kan.liang@...ux.intel.com>, Mark Rutland <mark.rutland@....com>,
Namhyung Kim <namhyung@...nel.org>, Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH v3] perf/core: Fix warning due to unordred pmu_ctx_list
…
> The follow testcase can trigger above warning:
following test case?
…
> The testcase first open a lbr event, so it will alloc task_ctx_data, and
test case? allocate?
> then open tracepoint and software events, so the parent ctx will have 3
context?
> different perf_event_pmu_contexts. When doing inherit, child ctx will
…
inheritance? context?
Please avoid a typo also in the summary phrase.
Regards,
Markus
Powered by blists - more mailing lists