All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: Will Deacon <will@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Leo Yan <leo.yan@linaro.org>, Ian Rogers <irogers@google.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Kemeng Shi <shikemeng@huawei.com>,
	"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Igor Lubashev <ilubashe@akamai.com>,
	Andi Kleen <ak@linux.intel.com>,
	Jin Yao <yao.jin@linux.intel.com>,
	Stephane Eranian <eranian@google.com>,
	James Clark <james.clark@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Perf tool: Enable Arm arch timer counter and arm-spe's timestamp
Date: Thu, 13 Aug 2020 10:05:23 -0300	[thread overview]
Message-ID: <20200813130523.GR13995@kernel.org> (raw)
In-Reply-To: <f3cbe339-0daa-054b-4c28-d8f130206a44@huawei.com>

Em Thu, Aug 13, 2020 at 01:08:02PM +0100, John Garry escreveu:
> On 13/08/2020 12:18, Will Deacon wrote:
> > [ Adding John, as I only just realised he wasn't on CC and we were talking
> >    about him! ]
> > 
> > On Thu, Aug 13, 2020 at 10:59:01AM +0100, Will Deacon wrote:
> > > On Wed, Aug 12, 2020 at 03:53:34PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > Em Wed, Aug 12, 2020 at 10:06:53AM -0600, Mathieu Poirier escreveu:
> > > > > The ARM SPE perf tools code is orphan and I don't have the cycles to
> > > > > pick it up.  Leo has spent a lot of time in that code and as such I
> > > > > suggest that he starts maintaining it, probably following the same
> > > > > kind of arrangement you and I have for coresight.
> > > > 
> > > > Thats ok with me, I think we should reflect that on the MAINTAINERS
> > > > file, right?
> > > > 
> > > > We have this already:
> > > > 
> > > > PERFORMANCE EVENTS SUBSYSTEM ARM64 PMU EVENTS
> > > > R:      John Garry <john.garry@huawei.com>
> > > > R:      Will Deacon <will@kernel.org>
> > > > L:      linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> > > > S:      Supported
> > > > F:      tools/perf/pmu-events/arch/arm64/
> > > > 
> > > > I think we should have entries for CoreSight and ARM SPE, one listing
> > > > you as the maintainer and the other listing Leo, right?
> > > 
> > > Fine by me. I'll continue to maintain the in-kernel SPE driver, but I'd love
> > > to see somebody step up to looking after the userspace code. It's seriously
> > > unloved on arm64 :(
> > > 
> > > I'd even be happy to see one or two M: entries added for
> > > tools/perf/pmu-events/arch/arm64/. I realistically don't have the time to
> > > take that on, but I'd be thrilled if any/all of John, Mathieu and Leo were
> > > to be listed there if they are willing to do so and can spare the time to
> > > look after it. Even just silly things like making sure the thing
> > > cross-compiles have been broken in the recent past, so it's not necessarily
> > > about handling huge amounts of incoming patches.
> > > 
> > > In other words, rather than slice up the arm64 parts of the perf tool, I'd
> > > argue in favour of a joint maintainership model for all the arm64 bits, if
> > > we have a few willing volunteers.
> 
> Right, it makes sense not to chop up too much, so happy to see "PERFORMANCE
> EVENTS SUBSYSTEM ARM64 PMU EVENTS" expanded in terms of scope and
> membership.

Discuss this as long as you need and then send me a patch for the
MAINTAINERS file with your conclusion.

Great to see this happening,

- Arnaldo

  reply	other threads:[~2020-08-13 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07  7:16 [PATCH v2 0/4] Perf tool: Enable Arm arch timer counter and arm-spe's timestamp Leo Yan
2020-08-07  7:16 ` [PATCH v2 1/4] perf tools: Support Arm arch timer counter Leo Yan
2020-08-20  2:56   ` liwei (GF)
2020-08-21  9:36     ` Leo Yan
2020-08-07  7:16 ` [PATCH v2 2/4] perf arm_arch_timer: Convert between counter and timestamp Leo Yan
2020-08-20  3:05   ` liwei (GF)
2020-08-07  7:16 ` [PATCH v2 3/4] perf arm_arch_timer: Test conversion " Leo Yan
2020-08-07  7:16 ` [PATCH v2 4/4] perf arm-spe: Enable timestamp with arch timer counter Leo Yan
2020-08-12 16:06 ` [PATCH v2 0/4] Perf tool: Enable Arm arch timer counter and arm-spe's timestamp Mathieu Poirier
2020-08-12 18:53   ` Arnaldo Carvalho de Melo
2020-08-13  1:54     ` Leo Yan
2020-08-13  9:59     ` Will Deacon
2020-08-13 11:18       ` Will Deacon
2020-08-13 12:08         ` John Garry
2020-08-13 13:05           ` Arnaldo Carvalho de Melo [this message]
2020-08-13 16:17     ` Mathieu Poirier

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=20200813130523.GR13995@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=ilubashe@akamai.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=shikemeng@huawei.com \
    --cc=will@kernel.org \
    --cc=yao.jin@linux.intel.com \
    /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.