All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, mingo@redhat.com
Subject: Re: [RFCv4 0/7]  arm_pmu/perf tools: play nicely with CPU PMU cpumasks
Date: Fri, 9 Sep 2016 10:31:31 +0100	[thread overview]
Message-ID: <20160909093131.GC20192@arm.com> (raw)
In-Reply-To: <20160908181657.GX10153@twins.programming.kicks-ass.net>

On Thu, Sep 08, 2016 at 08:16:57PM +0200, Peter Zijlstra wrote:
> On Thu, Sep 08, 2016 at 01:25:02PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Sep 08, 2016 at 11:21:45AM +0100, Mark Rutland escreveu:
> > > Hi,
> > > 
> > > I'm trying to make the perf tool play better with PMUs in heterogeneous systems
> > > (e.g. big.LITTLE), where there are several logical PMUs, each covering a subset
> > > of CPUs.
> > 
> > So I added 6/7 and 7/7 to my local perf/core branch, I think they can go
> > before the others, Peter, do you want me to take the kernel parts as
> > well?
> 
> arm pmu stuff usually goes through the arm tree. Up to Mark I suppose.

I can queue the kernel bits once I've reviewed them (will try to take a
look today).

Will

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFCv4 0/7]  arm_pmu/perf tools: play nicely with CPU PMU cpumasks
Date: Fri, 9 Sep 2016 10:31:31 +0100	[thread overview]
Message-ID: <20160909093131.GC20192@arm.com> (raw)
In-Reply-To: <20160908181657.GX10153@twins.programming.kicks-ass.net>

On Thu, Sep 08, 2016 at 08:16:57PM +0200, Peter Zijlstra wrote:
> On Thu, Sep 08, 2016 at 01:25:02PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Sep 08, 2016 at 11:21:45AM +0100, Mark Rutland escreveu:
> > > Hi,
> > > 
> > > I'm trying to make the perf tool play better with PMUs in heterogeneous systems
> > > (e.g. big.LITTLE), where there are several logical PMUs, each covering a subset
> > > of CPUs.
> > 
> > So I added 6/7 and 7/7 to my local perf/core branch, I think they can go
> > before the others, Peter, do you want me to take the kernel parts as
> > well?
> 
> arm pmu stuff usually goes through the arm tree. Up to Mark I suppose.

I can queue the kernel bits once I've reviewed them (will try to take a
look today).

Will

  reply	other threads:[~2016-09-09  9:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 10:21 [RFCv4 0/7] arm_pmu/perf tools: play nicely with CPU PMU cpumasks Mark Rutland
2016-09-08 10:21 ` Mark Rutland
2016-09-08 10:21 ` [RFCv4 1/7] drivers/perf: arm_pmu: add common attr group fields Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-09 10:25   ` Will Deacon
2016-09-09 10:25     ` Will Deacon
2016-09-09 11:05     ` Mark Rutland
2016-09-09 11:05       ` Mark Rutland
2016-09-08 10:21 ` [RFCv4 2/7] arm64: perf: move to common attr_group fields Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-08 10:21 ` [RFCv4 3/7] arm: " Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-08 10:21 ` [RFCv4 4/7] drivers/perf: arm_pmu: only use common attr_groups Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-08 10:21 ` [RFCv4 5/7] drivers/perf: arm_pmu: expose a cpumask in sysfs Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-09 10:24   ` Will Deacon
2016-09-09 10:24     ` Will Deacon
2016-09-09 11:04     ` Mark Rutland
2016-09-09 11:04       ` Mark Rutland
2016-09-08 10:21 ` [RFCv4 6/7] perf: util: only open events on CPUs an evsel permits Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-09  5:53   ` [tip:perf/core] perf evlist: Only " tip-bot for Mark Rutland
2016-09-08 10:21 ` [RFCv4 7/7] perf: util: support alternative sysfs cpumask Mark Rutland
2016-09-08 10:21   ` Mark Rutland
2016-09-09  5:54   ` [tip:perf/core] perf pmu: Support " tip-bot for Mark Rutland
2016-09-08 10:38 ` [RFCv4 0/7] arm_pmu/perf tools: play nicely with CPU PMU cpumasks Will Deacon
2016-09-08 10:38   ` Will Deacon
2016-09-08 11:29   ` Mark Rutland
2016-09-08 11:29     ` Mark Rutland
2016-09-08 16:25 ` Arnaldo Carvalho de Melo
2016-09-08 16:25   ` Arnaldo Carvalho de Melo
2016-09-08 18:16   ` Peter Zijlstra
2016-09-08 18:16     ` Peter Zijlstra
2016-09-09  9:31     ` Will Deacon [this message]
2016-09-09  9:31       ` Will Deacon

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=20160909093131.GC20192@arm.com \
    --to=will.deacon@arm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.