Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: John Garry <john.garry@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	will@kernel.org, linux-kernel@vger.kernel.org, acme@kernel.org,
	Jiri Olsa <jolsa@redhat.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: Add entries for CoreSight and Arm SPE
Date: Wed, 19 Aug 2020 10:24:02 +0800	[thread overview]
Message-ID: <20200819022402.GB9556@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <ede047ea-ad6a-1f7e-d597-b47bc87271c3@huawei.com>

On Tue, Aug 18, 2020 at 06:54:28PM +0100, John Garry wrote:
> On 17/08/2020 20:31, Mathieu Poirier wrote:
> > Add entries for perf tools elements related to the support of
> > Arm CoreSight and Arm SPE.
> 
> Thanks for doing this...
> 
> > 
> > Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> > ---
> >   MAINTAINERS | 10 ++++++++++
> >   1 file changed, 10 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 4e2698cc7e23..f9bb76baeec9 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -13427,8 +13427,18 @@ F:	tools/perf/
> >   PERFORMANCE EVENTS SUBSYSTEM ARM64 PMU EVENTS
> >   R:	John Garry <john.garry@huawei.com>
> >   R:	Will Deacon <will@kernel.org>
> > +R:	Mathieu Poirier <mathieu.poirier@linaro.org>
> > +R:	Leo Yan <leo.yan@linaro.org>
> >   L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> >   S:	Supported
> > +F:	tools/build/feature/test-libopencsd.c
> > +F:	tools/perf/arch/arm/util/auxtrace.c
> > +F:	tools/perf/arch/arm/util/cs-etm.*
> > +F:	tools/perf/arch/arm/util/pmu.c
> > +F:	tools/perf/arch/arm64/util/arm-spe.c
> > +F:	tools/perf/util/arm-spe.h
> > +F:	tools/perf/util/cs-etm-decoder/*
> > +F:	tools/perf/util/cs-etm.*
> 
> But from the previous discussion, I thought that we wanted an entry to cover
> all tools/perf/arch/arm64/ and other related folders. Or was it just put all
> special interest parts (like SPE support) under one entry and leave the
> other arm/arm64 parts to be caught by "PERFORMANCE EVENTS SUBSYSTEM" entry?

Yes, I think we need to add below two items for Arm SPE:

F:	tools/perf/util/arm-spe-decoder/*
F:	tools/perf/util/arm-spe.*

Thanks,
Leo

> >   F:	tools/perf/pmu-events/arch/arm64/
> >   PERSONALITY HANDLING
> > 
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-08-19  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200817193140.3659956-1-mathieu.poirier@linaro.org>
2020-08-18 17:54 ` [PATCH] MAINTAINERS: Add entries for CoreSight and Arm SPE John Garry
2020-08-19  2:24   ` Leo Yan [this message]
2020-08-19 17:01   ` Mathieu Poirier
2020-08-19 17:30     ` Will Deacon
2020-08-19 19:26       ` Mathieu Poirier
2020-08-20  7:50         ` John Garry

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=20200819022402.GB9556@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=acme@kernel.org \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=will@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