From: Song Liu <songliubraving@fb.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Kernel Team <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>,
kernel test robot <rong.a.chen@intel.com>
Subject: Re: [PATCH v12] perf: Sharing PMU counters across compatible events
Date: Thu, 9 Apr 2020 20:40:25 +0000 [thread overview]
Message-ID: <47BDB3EA-2DF6-4FB1-AF06-F63A342861DF@fb.com> (raw)
In-Reply-To: <20200331075533.2347393-1-songliubraving@fb.com>
Hi Peter,
> On Mar 31, 2020, at 12:55 AM, Song Liu <songliubraving@fb.com> wrote:
>
> This patch tries to enable PMU sharing. When multiple perf_events are
> counting the same metric, they can share the hardware PMU counter. We
> call these events as "compatible events".
>
> The PMU sharing are limited to events within the same perf_event_context
> (ctx). When a event is installed or enabled, search the ctx for compatible
> events. This is implemented in perf_event_setup_dup(). One of these
> compatible events are picked as the master (stored in event->dup_master).
> Similarly, when the event is removed or disabled, perf_event_remove_dup()
> is used to clean up sharing.
>
> If the master event is a cgroup event or a event in a group, it is
> possible that some slave events are ACTIVE, but the master event is not.
> To handle this scenario, we introduced PERF_EVENT_STATE_ENABLED. Also,
> since PMU drivers write into event->count, master event needs another
> variable (master_count) for the reading of this event.
>
> On the critical paths (add, del read), sharing PMU counters doesn't
> increase the complexity. Helper functions event_pmu_[add|del|read]() are
> introduced to cover these cases. All these functions have O(1) time
> complexity.
>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Alexey Budankov <alexey.budankov@linux.intel.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Tejun Heo <tj@kernel.org>
> Reported-by: kernel test robot <rong.a.chen@intel.com>
> Signed-off-by: Song Liu <songliubraving@fb.com>
Could you please share your comments on this version?
Thanks,
Song
next prev parent reply other threads:[~2020-04-09 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 7:55 Song Liu
2020-04-09 20:40 ` Song Liu [this message]
2020-04-20 23:04 ` Peter Zijlstra
2020-04-21 1:13 ` Song Liu
2020-04-21 7:18 ` Peter Zijlstra
2020-04-29 20:44 ` 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=47BDB3EA-2DF6-4FB1-AF06-F63A342861DF@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=acme@redhat.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rong.a.chen@intel.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
all inboxes | Powered by JetHome®