lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ede047ea-ad6a-1f7e-d597-b47bc87271c3@huawei.com>
Date:   Tue, 18 Aug 2020 18:54:28 +0100
From:   John Garry <john.garry@...wei.com>
To:     Mathieu Poirier <mathieu.poirier@...aro.org>, <acme@...nel.org>,
        <will@...nel.org>, <leo.yan@...aro.org>
CC:     <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Jiri Olsa <jolsa@...hat.com>,
        Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH] MAINTAINERS: Add entries for CoreSight and Arm SPE

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@...aro.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@...wei.com>
>   R:	Will Deacon <will@...nel.org>
> +R:	Mathieu Poirier <mathieu.poirier@...aro.org>
> +R:	Leo Yan <leo.yan@...aro.org>
>   L:	linux-arm-kernel@...ts.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?

Cheers,
John

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ