public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: 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, kernel-team@fb.com,
	alexey.budankov@linux.intel.com
Subject: Re: [RFC] Sharing PMU counters across compatible events
Date: Wed, 13 Dec 2017 08:18:29 -0800	[thread overview]
Message-ID: <20171213161829.GV3919388@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171212223736.llqgzpit4n2klhwg@hirez.programming.kicks-ass.net>

Hello, Peter.

On Tue, Dec 12, 2017 at 11:37:36PM +0100, Peter Zijlstra wrote:
> That would be a fairly massive change from how perf works today. And the
> obvious pain point would be changing the per-cpu event set, which would
> mean recomputing all possible combinations of task sets.
> 
> Also note that each context (cpu,task) is allowed to have more events
> than fit on the PMU, at which point we'll start rotating events. Do we
> also pre-compute all possible rotation sets?
> 
> Just not quite seeing this..

Yeah, right.  Will think more about it

Thanks.

-- 
tejun

      reply	other threads:[~2017-12-13 16:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 14:19 [RFC] Sharing PMU counters across compatible events Tejun Heo
2017-12-06 11:42 ` Jiri Olsa
2017-12-11 15:34   ` Tejun Heo
2017-12-13 10:18     ` Jiri Olsa
2017-12-13 16:15       ` Tejun Heo
2017-12-06 12:35 ` Peter Zijlstra
2017-12-11 15:47   ` Tejun Heo
2017-12-12 22:37     ` Peter Zijlstra
2017-12-13 16:18       ` Tejun Heo [this message]

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=20171213161829.GV3919388@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=kernel-team@fb.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