From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@kernel.org>,
Alexey Budankov <alexey.budankov@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v8] perf: Sharing PMU counters across compatible events
Date: Thu, 12 Dec 2019 14:49:51 +0100 [thread overview]
Message-ID: <20191212134951.GX2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191207002447.2976319-1-songliubraving@fb.com>
On Fri, Dec 06, 2019 at 04:24:47PM -0800, Song Liu wrote:
> @@ -750,6 +752,16 @@ struct perf_event {
> void *security;
> #endif
> struct list_head sb_list;
> +
> + /* for PMU sharing */
> + struct perf_event *dup_master;
> + /* check event_sync_dup_count() for the use of dup_base_* */
> + u64 dup_base_count;
> + u64 dup_base_child_count;
> + /* when this event is master, read from master*count */
> + local64_t master_count;
> + atomic64_t master_child_count;
> + int dup_active_count;
> #endif /* CONFIG_PERF_EVENTS */
> };
> +/* PMU sharing aware version of event->pmu->add() */
> +static int event_pmu_add(struct perf_event *event,
> + struct perf_event_context *ctx)
> +{
> + struct perf_event *master;
> + int ret;
> +
> + /* no sharing, just do event->pmu->add() */
> + if (!event->dup_master)
> + return event->pmu->add(event, PERF_EF_START);
Possibly we should look at the location of perf_event::dup_master to be
in a hot cacheline. Because I'm thinking you just added a guaranteed
miss here.
> +
> + master = event->dup_master;
> +
> + if (!master->dup_active_count) {
> + ret = event->pmu->add(master, PERF_EF_START);
> + if (ret)
> + return ret;
> +
> + if (master != event)
> + perf_event_set_state(master, PERF_EVENT_STATE_ENABLED);
> + }
> +
> + master->dup_active_count++;
> + master->pmu->read(master);
> + event->dup_base_count = local64_read(&master->count);
> + event->dup_base_child_count = atomic64_read(&master->child_count);
> + return 0;
> +}
> +/* PMU sharing aware version of event->pmu->del() */
> +static void event_pmu_del(struct perf_event *event,
> + struct perf_event_context *ctx)
> +{
> + struct perf_event *master;
> +
> + if (event->dup_master == NULL) {
> + event->pmu->del(event, 0);
> + return;
> + }
How about you write it exactly like the add version:
if (!event->dup_master)
return event->pmu->del(event, 0);
?
> +
> + master = event->dup_master;
> + event_sync_dup_count(event, master);
> + if (--master->dup_active_count == 0) {
> + event->pmu->del(master, 0);
> + perf_event_set_state(master, PERF_EVENT_STATE_INACTIVE);
> + } else if (master == event) {
> + perf_event_set_state(master, PERF_EVENT_STATE_ENABLED);
> + }
> +}
> +
> +/* PMU sharing aware version of event->pmu->read() */
> +static void event_pmu_read(struct perf_event *event)
> +{
> + if (event->dup_master == NULL) {
> + event->pmu->read(event);
> + return;
> + }
And here too.
> + event_sync_dup_count(event, event->dup_master);
> +}
next prev parent reply other threads:[~2019-12-12 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 0:24 [PATCH v8] perf: Sharing PMU counters across compatible events Song Liu
2019-12-11 18:50 ` Song Liu
2019-12-12 13:42 ` Peter Zijlstra
2019-12-12 15:18 ` Song Liu
2019-12-12 13:49 ` Peter Zijlstra [this message]
2019-12-12 15:37 ` Song Liu
2019-12-12 15:44 ` Peter Zijlstra
2019-12-12 15:47 ` Song Liu
2019-12-12 15:39 ` Peter Zijlstra
2019-12-12 15:45 ` Song Liu
2019-12-12 16:00 ` Song Liu
2019-12-12 18:01 ` Song Liu
2019-12-12 18:52 ` Peter Zijlstra
2019-12-12 23:49 ` Song Liu
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=20191212134951.GX2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=songliubraving@fb.com \
--cc=tj@kernel.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