From: Luo Gengkun <luogengkun@huaweicloud.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, davidcc@google.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
luogengkun@huaweicloud.com
Subject: [PATCH v2 0/2] Fix perf cgroup problem
Date: Wed, 4 Jun 2025 03:39:22 +0000 [thread overview]
Message-ID: <20250604033924.3914647-1-luogengkun@huaweicloud.com> (raw)
---
Changes in v2:
1. First patch adapted based on the lastest mainline code
2. update commit message for the second patch.
Link to v1: https://lore.kernel.org/all/20250514064758.4156497-1-luogengkun@huaweicloud.com/
Luo Gengkun (2):
perf/core: Fix nr_cgroups/cpuctx->cgrp is not updated correctly
perf/core: Fix WARN_ON_ONCE(cpuctx->ctx.nr_cgroups == 0) in
perf_cgroup_switch
kernel/events/core.c | 24 ++++++++----------------
1 file changed, 8 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2025-06-04 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 3:39 Luo Gengkun [this message]
2025-06-04 3:39 ` [PATCH v2 1/2] perf/core: Fix nr_cgroups/cpuctx->cgrp is not updated correctly Luo Gengkun
2025-06-04 9:19 ` Peter Zijlstra
2025-06-04 9:42 ` Luo Gengkun
2025-06-04 3:39 ` [PATCH v2 2/2] perf/core: Fix WARN_ON_ONCE(cpuctx->ctx.nr_cgroups == 0) in perf_cgroup_switch Luo Gengkun
2025-06-04 10:00 ` Peter Zijlstra
2025-06-05 3:55 ` Luo Gengkun
2025-06-05 7:36 ` Peter Zijlstra
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=20250604033924.3914647-1-luogengkun@huaweicloud.com \
--to=luogengkun@huaweicloud.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=davidcc@google.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).