From: Peter Zijlstra <peterz@infradead.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, songliubraving@fb.com,
eranian@google.com, alexey.budankov@linux.intel.com,
ak@linux.intel.com, mark.rutland@arm.com, megha.dey@intel.com,
frederic@kernel.org, maddy@linux.ibm.com, irogers@google.com,
kim.phillips@amd.com, linux-kernel@vger.kernel.org,
santosh.shukla@amd.com
Subject: Re: [RFC v2] perf: Rewrite core context handling
Date: Mon, 13 Jun 2022 16:43:52 +0200 [thread overview]
Message-ID: <YqdNKJllCVMci3ov@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <YqdLH+ZU/sf4n0pa@hirez.programming.kicks-ass.net>
On Mon, Jun 13, 2022 at 04:35:11PM +0200, Peter Zijlstra wrote:
> @@ -3652,17 +3697,28 @@ static noinline int visit_groups_merge(s
> .size = ARRAY_SIZE(itrs),
> };
> /* Events not within a CPU context may be on any CPU. */
> - __heap_add(&event_heap, perf_event_groups_first(groups, -1, NULL));
> + __heap_add(&event_heap, perf_event_groups_first(groups, -1, pmu, NULL));
> }
> evt = event_heap.data;
>
> - __heap_add(&event_heap, perf_event_groups_first(groups, cpu, NULL));
> + __heap_add(&event_heap, perf_event_groups_first(groups, cpu, pmu, NULL));
>
> #ifdef CONFIG_CGROUP_PERF
> for (; css; css = css->parent)
> - __heap_add(&event_heap, perf_event_groups_first(groups, cpu, css->cgroup));
> + __heap_add(&event_heap, perf_event_groups_first(groups, cpu, pmu, css->cgroup));
> #endif
>
> + if (event_heap.nr) {
> + /*
> + * XXX: For now, visit_groups_merge() gets called with pmu
> + * pointer never NULL. But these functions needs to be called
> + * once for each pmu if I implement pmu=NULL optimization.
> + */
> + __link_epc((*evt)->pmu_ctx);
> + perf_assert_pmu_disabled((*evt)->pmu_ctx->pmu);
> + }
> +
> +
> min_heapify_all(&event_heap, &perf_min_heap);
>
> while (event_heap.nr) {
> @@ -3741,39 +3799,67 @@ static int merge_sched_in(struct perf_ev
> return 0;
> }
>
> -static void
> -ctx_pinned_sched_in(struct perf_event_context *ctx,
> - struct perf_cpu_context *cpuctx)
> +static void ctx_pinned_sched_in(struct perf_event_context *ctx, struct pmu *pmu)
> {
> + struct perf_event_pmu_context *pmu_ctx;
> int can_add_hw = 1;
>
> - if (ctx != &cpuctx->ctx)
> - cpuctx = NULL;
> -
> - visit_groups_merge(cpuctx, &ctx->pinned_groups,
> - smp_processor_id(),
> - merge_sched_in, &can_add_hw);
> + if (pmu) {
> + visit_groups_merge(ctx, &ctx->pinned_groups,
> + smp_processor_id(), pmu,
> + merge_sched_in, &can_add_hw);
> + } else {
> + /*
> + * XXX: This can be optimized for per-task context by calling
> + * visit_groups_merge() only once with:
> + * 1) pmu=NULL
> + * 2) Ignoring pmu in perf_event_groups_cmp() when it's NULL
> + * 3) Making can_add_hw a per-pmu variable
> + *
> + * Though, it can not be opimized for per-cpu context because
> + * per-cpu rb-tree consist of pmu-subtrees and pmu-subtrees
> + * consist of cgroup-subtrees. i.e. a cgroup events of same
> + * cgroup but different pmus are seperated out into respective
> + * pmu-subtrees.
> + */
> + list_for_each_entry(pmu_ctx, &ctx->pmu_ctx_list, pmu_ctx_entry) {
> + can_add_hw = 1;
> + visit_groups_merge(ctx, &ctx->pinned_groups,
> + smp_processor_id(), pmu_ctx->pmu,
> + merge_sched_in, &can_add_hw);
> + }
> + }
> }
I'm not sure I follow.. task context can have multiple PMUs just the
same as CPU context can, that's more or less the entire point of the
patch.
next prev parent reply other threads:[~2022-06-13 18:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 13:47 [RFC v2] perf: Rewrite core context handling Ravi Bangoria
2022-01-17 7:18 ` [perf] f7cf7134e4: WARNING:at_kernel/events/core.c:#__pmu_ctx_sched_out kernel test robot
2022-01-31 4:43 ` [RFC v2] perf: Rewrite core context handling Ravi Bangoria
2022-06-13 14:35 ` Peter Zijlstra
2022-06-13 14:36 ` Peter Zijlstra
2022-06-13 14:38 ` Peter Zijlstra
2022-08-02 6:11 ` Ravi Bangoria
2022-08-22 15:29 ` Peter Zijlstra
2022-08-22 15:43 ` Peter Zijlstra
2022-08-22 16:37 ` Ravi Bangoria
2022-08-23 4:20 ` Ravi Bangoria
2022-08-29 3:54 ` Ravi Bangoria
2022-08-23 6:30 ` Peter Zijlstra
2022-08-29 4:00 ` Ravi Bangoria
2022-08-29 11:58 ` Peter Zijlstra
2022-08-22 16:52 ` Peter Zijlstra
2022-08-23 4:57 ` Ravi Bangoria
2022-06-13 14:41 ` Peter Zijlstra
2022-08-22 14:38 ` Ravi Bangoria
2022-06-13 14:43 ` Peter Zijlstra [this message]
2022-08-02 6:16 ` Ravi Bangoria
2022-08-23 8:57 ` Peter Zijlstra
2022-08-24 5:07 ` Ravi Bangoria
2022-08-24 7:27 ` Peter Zijlstra
2022-08-24 7:53 ` Ravi Bangoria
2022-06-13 14:55 ` Peter Zijlstra
2022-08-02 6:10 ` Ravi Bangoria
2022-08-22 16:44 ` Peter Zijlstra
2022-08-23 4:46 ` Ravi Bangoria
2022-06-17 13:36 ` Peter Zijlstra
2022-08-24 10:13 ` Peter Zijlstra
2022-06-27 4:18 ` Ravi Bangoria
2022-08-02 6:06 ` Ravi Bangoria
2022-08-24 12:15 ` Peter Zijlstra
2022-08-24 14:59 ` Peter Zijlstra
2022-08-25 5:39 ` Ravi Bangoria
2022-08-25 9:17 ` Peter Zijlstra
2022-08-25 11:03 ` Ravi Bangoria
2022-08-02 6:13 ` Ravi Bangoria
2022-08-23 7:10 ` Peter Zijlstra
2022-08-02 6:17 ` Ravi Bangoria
2022-08-23 7:26 ` Peter Zijlstra
2022-08-23 15:14 ` Ravi Bangoria
2022-08-22 14:40 ` Ravi Bangoria
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=YqdNKJllCVMci3ov@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=eranian@google.com \
--cc=frederic@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=megha.dey@intel.com \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.com \
--cc=santosh.shukla@amd.com \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).