From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@redhat.com, tglx@linutronix.de, bp@alien8.de,
acme@kernel.org, namhyung@kernel.org, irogers@google.com,
linux-kernel@vger.kernel.org, ak@linux.intel.com,
eranian@google.com
Subject: Re: [PATCH V10 1/7] perf: Save PMU specific data in task_struct
Date: Mon, 17 Mar 2025 12:10:45 +0100 [thread overview]
Message-ID: <20250317111045.GA36386@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250314172700.438923-1-kan.liang@linux.intel.com>
Kan, can you please do a patch failing perf_pmu_register() is there's
more than one pmu with one of the kmem_cache things on?
Because the current thing very much cannot deal with that case.
next prev parent reply other threads:[~2025-03-17 11:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 17:26 [PATCH V10 1/7] perf: Save PMU specific data in task_struct kan.liang
2025-03-14 17:26 ` [PATCH V10 2/7] locking/percpu-rwsem: Add guard support kan.liang
2025-03-17 10:34 ` [tip: perf/core] " tip-bot2 for Peter Zijlstra (Intel)
2025-03-14 17:26 ` [PATCH V10 3/7] perf: attach/detach PMU specific data kan.liang
2025-03-14 21:05 ` Peter Zijlstra
2025-03-17 10:34 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-03-14 17:26 ` [PATCH V10 4/7] perf: Supply task information to sched_task() kan.liang
2025-03-17 10:34 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-03-14 17:26 ` [PATCH V10 5/7] perf/x86/lbr: Fix shorter LBRs call stacks for the system-wide mode kan.liang
2025-03-17 10:34 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-03-14 17:26 ` [PATCH V10 6/7] perf/x86: Remove swap_task_ctx() kan.liang
2025-03-17 10:34 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-03-14 17:27 ` [PATCH V10 7/7] perf: Clean up pmu specific data kan.liang
2025-03-17 10:34 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-03-17 10:34 ` [tip: perf/core] perf: Save PMU specific data in task_struct tip-bot2 for Kan Liang
2025-03-17 11:10 ` Peter Zijlstra [this message]
2025-03-24 14:07 ` [PATCH V10 1/7] " Liang, Kan
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=20250317111045.GA36386@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.