mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	Kernel Team <Kernel-team@fb.com>,
	David Carrillo Cisneros <davidca@fb.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	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 v7] perf: Sharing PMU counters across compatible events
Date: Mon, 25 Nov 2019 09:39:49 +0000	[thread overview]
Message-ID: <0906DAE0-52F4-4F58-8912-19A45ADAA189@fb.com> (raw)
In-Reply-To: <20191125092202.GB20575@krava>



> On Nov 24, 2019, at 11:22 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> 
> On Fri, Nov 22, 2019 at 07:50:06PM +0000, Song Liu wrote:
>> 
>> 
>>> On Nov 22, 2019, at 11:33 AM, Jiri Olsa <jolsa@redhat.com> wrote:
>>> 
>>> On Fri, Nov 15, 2019 at 03:55:04PM -0800, Song Liu 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.
>>>> 
>>>> A new state PERF_EVENT_STATE_ENABLED is introduced for the master event.
>>>> This state is used when the slave event is ACTIVE, but the master event
>>>> is not.
>>>> 
>>>> 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>
>>>> Signed-off-by: Song Liu <songliubraving@fb.com>
>>>> 
>>>> ---
>>>> Changes in v7:
>>>> Major rewrite to avoid allocating extra master event.
>>> 
>>> hi,
>>> what is this based on? I can't apply it on tip/master:
>>> 
>>> 	Applying: perf: Sharing PMU counters across compatible events
>>> 	error: patch failed: include/linux/perf_event.h:722
>>> 	error: include/linux/perf_event.h: patch does not apply
>>> 	Patch failed at 0001 perf: Sharing PMU counters across compatible events
>>> 	hint: Use 'git am --show-current-patch' to see the failed patch
>>> 	When you have resolved this problem, run "git am --continue".
>>> 	If you prefer to skip this patch, run "git am --skip" instead.
>>> 	To restore the original branch and stop patching, run "git am --abort".
>> 
> 
> hi,
> I'm getting warning below when running 'perf test',
> not sure what's the reason yet..

Thanks for the heads-up. I will try to look into it. I am on vacation this 
week, so please expect some delay. 

Best,
Song





  reply	other threads:[~2019-11-25  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 23:55 Song Liu
2019-11-19 15:28 ` Song Liu
2019-11-22 19:33 ` Jiri Olsa
2019-11-22 19:50   ` Song Liu
2019-11-25  9:22     ` Jiri Olsa
2019-11-25  9:39       ` Song Liu [this message]
2019-12-06  0:47     ` [perf] 9dc510db74: perf-sanity-tests.Read_samples_using_the_mmap_interface.fail kernel test robot
2019-11-28  8:30 ` [PATCH v7] perf: Sharing PMU counters across compatible events Jiri Olsa
2019-12-04 22:16   ` 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=0906DAE0-52F4-4F58-8912-19A45ADAA189@fb.com \
    --to=songliubraving@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=acme@redhat.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=davidca@fb.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --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®