From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, ak@linux.intel.com,
eranian@google.com
Subject: Re: [PATCH] perf cgroups: Don't rotate events for cgroups unnecessarily
Date: Thu, 13 Jun 2019 12:12:56 -0400 [thread overview]
Message-ID: <5084acfa-59a4-996f-bb1d-69fbbac01b87@linux.intel.com> (raw)
In-Reply-To: <20190601082722.44543-1-irogers@google.com>
On 6/1/2019 4:27 AM, Ian Rogers wrote:
> Currently perf_rotate_context assumes that if the context's nr_events !=
> nr_active a rotation is necessary for perf event multiplexing. With
> cgroups, nr_events is the total count of events for all cgroups and
> nr_active will not include events in a cgroup other than the current
> task's. This makes rotation appear necessary for cgroups when it is not.
>
> Add a perf_event_context flag that is set when rotation is necessary.
> Clear the flag during sched_out and set it when a flexible sched_in
> fails due to resources.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> include/linux/perf_event.h | 5 +++++
> kernel/events/core.c | 42 +++++++++++++++++++++++---------------
> 2 files changed, 30 insertions(+), 17 deletions(-)
>
> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> index 15a82ff0aefe..7ab6c251aa3d 100644
> --- a/include/linux/perf_event.h
> +++ b/include/linux/perf_event.h
> @@ -747,6 +747,11 @@ struct perf_event_context {
> int nr_stat;
> int nr_freq;
> int rotate_disable;
> + /*
> + * Set when nr_events != nr_active, except tolerant to events not
> + * needing to be active due to scheduling constraints, such as cgroups.
> + */
> + int rotate_necessary;
It looks like the rotate_necessary is only useful for cgroup and cpuctx.
Why not move it to struct perf_cpu_context and under #ifdef
CONFIG_CGROUP_PERF?
And rename it cgrp_rotate_necessary?
Thanks,
Kan
> refcount_t refcount;
> struct task_struct *task;
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index abbd4b3b96c2..41ae424b9f1d 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -2952,6 +2952,12 @@ static void ctx_sched_out(struct perf_event_context *ctx,
> if (!ctx->nr_active || !(is_active & EVENT_ALL))
> return;
>
> + /*
> + * If we had been multiplexing, no rotations are necessary now no events
> + * are active.
> + */
> + ctx->rotate_necessary = 0;
> +
> perf_pmu_disable(ctx->pmu);
> if (is_active & EVENT_PINNED) {
> list_for_each_entry_safe(event, tmp, &ctx->pinned_active, active_list)
> @@ -3325,6 +3331,15 @@ static int flexible_sched_in(struct perf_event *event, void *data)
> sid->can_add_hw = 0;
> }
>
> + /*
> + * If the group wasn't scheduled then set that multiplexing is necessary
> + * for the context. Note, this won't be set if the event wasn't
> + * scheduled due to event_filter_match failing due to the earlier
> + * return.
> + */
> + if (event->state == PERF_EVENT_STATE_INACTIVE)
> + sid->ctx->rotate_necessary = 1;
> +
> return 0;
> }
>
> @@ -3690,24 +3705,17 @@ ctx_first_active(struct perf_event_context *ctx)
> static bool perf_rotate_context(struct perf_cpu_context *cpuctx)
> {
> struct perf_event *cpu_event = NULL, *task_event = NULL;
> - bool cpu_rotate = false, task_rotate = false;
> - struct perf_event_context *ctx = NULL;
> + struct perf_event_context *task_ctx = NULL;
> + int cpu_rotate, task_rotate;
>
> /*
> * Since we run this from IRQ context, nobody can install new
> * events, thus the event count values are stable.
> */
>
> - if (cpuctx->ctx.nr_events) {
> - if (cpuctx->ctx.nr_events != cpuctx->ctx.nr_active)
> - cpu_rotate = true;
> - }
> -
> - ctx = cpuctx->task_ctx;
> - if (ctx && ctx->nr_events) {
> - if (ctx->nr_events != ctx->nr_active)
> - task_rotate = true;
> - }
> + cpu_rotate = cpuctx->ctx.rotate_necessary;
> + task_ctx = cpuctx->task_ctx;
> + task_rotate = task_ctx ? task_ctx->rotate_necessary : 0;
>
> if (!(cpu_rotate || task_rotate))
> return false;
> @@ -3716,7 +3724,7 @@ static bool perf_rotate_context(struct perf_cpu_context *cpuctx)
> perf_pmu_disable(cpuctx->ctx.pmu);
>
> if (task_rotate)
> - task_event = ctx_first_active(ctx);
> + task_event = ctx_first_active(task_ctx);
> if (cpu_rotate)
> cpu_event = ctx_first_active(&cpuctx->ctx);
>
> @@ -3724,17 +3732,17 @@ static bool perf_rotate_context(struct perf_cpu_context *cpuctx)
> * As per the order given at ctx_resched() first 'pop' task flexible
> * and then, if needed CPU flexible.
> */
> - if (task_event || (ctx && cpu_event))
> - ctx_sched_out(ctx, cpuctx, EVENT_FLEXIBLE);
> + if (task_event || (task_ctx && cpu_event))
> + ctx_sched_out(task_ctx, cpuctx, EVENT_FLEXIBLE);
> if (cpu_event)
> cpu_ctx_sched_out(cpuctx, EVENT_FLEXIBLE);
>
> if (task_event)
> - rotate_ctx(ctx, task_event);
> + rotate_ctx(task_ctx, task_event);
> if (cpu_event)
> rotate_ctx(&cpuctx->ctx, cpu_event);
>
> - perf_event_sched_in(cpuctx, ctx, current);
> + perf_event_sched_in(cpuctx, task_ctx, current);
>
> perf_pmu_enable(cpuctx->ctx.pmu);
> perf_ctx_unlock(cpuctx, cpuctx->task_ctx);
>
next prev parent reply other threads:[~2019-06-13 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 8:27 Ian Rogers
2019-06-13 16:12 ` Liang, Kan [this message]
2019-06-14 19:10 ` Stephane Eranian
2019-06-14 21:43 ` Liang, Kan
2019-06-20 23:08 ` Ian Rogers
2019-06-21 8:24 ` Peter Zijlstra
2019-06-21 18:01 ` Ian Rogers
2019-06-24 7:55 ` Peter Zijlstra
2019-06-27 21:47 ` Ian Rogers
2019-08-23 10:43 ` Ganapatrao Kulkarni
2019-08-23 11:59 ` Peter Zijlstra
2019-08-23 12:56 ` Ganapatrao Kulkarni
2019-08-23 13:03 ` Peter Zijlstra
2019-09-18 7:21 ` Ganapatrao Kulkarni
2019-10-15 4:43 ` Ganapatrao Kulkarni
2019-06-25 8:43 ` [tip:perf/core] perf/cgroups: " tip-bot for Ian Rogers
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=5084acfa-59a4-996f-bb1d-69fbbac01b87@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome