mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Luo Gengkun <luogengkun@huaweicloud.com>,
	linux-perf-users@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [PATCH v3] perf/core: Fix warning due to unordred pmu_ctx_list
Date: Sat, 8 Feb 2025 18:37:34 +0100	[thread overview]
Message-ID: <a926f05d-03ec-4c78-83f2-3a50299e8be4@web.de> (raw)
In-Reply-To: <20250122073356.1824736-1-luogengkun@huaweicloud.com>

…
> 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

  parent reply	other threads:[~2025-02-08 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  7:33 Luo Gengkun
2025-02-08 11:38 ` Luo Gengkun
2025-02-08 17:37 ` Markus Elfring [this message]
2025-02-24 18:36 ` [tip: perf/urgent] perf/core: Order the PMU list to fix warning about unordered pmu_ctx_list tip-bot2 for Luo Gengkun

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=a926f05d-03ec-4c78-83f2-3a50299e8be4@web.de \
    --to=markus.elfring@web.de \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=luogengkun@huaweicloud.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    /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
all inboxes | Powered by JetHome®