[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6333f002-1213-0e20-0fcc-b3bfc0723b97@arm.com>
Date: Mon, 7 Sep 2020 15:10:37 +0100
From: Suzuki K Poulose <suzuki.poulose@....com>
To: leo.yan@...aro.org, acme@...nel.org, mathieu.poirier@...aro.org,
mike.leach@...aro.org, peterz@...radead.org, mingo@...hat.com,
mark.rutland@....com, alexander.shishkin@...ux.intel.com,
jolsa@...hat.com, namhyung@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7] perf test: Introduce script for Arm CoreSight testing
On 09/07/2020 02:01 PM, Leo Yan wrote:
> We need a simple method to test Perf with Arm CoreSight drivers, this
> could be used for smoke testing when new patch is coming for perf or
> CoreSight drivers, and we also can use the test to confirm if the
> CoreSight has been enabled successfully on new platforms.
>
> This patch introduces the shell script test_arm_coresight.sh which is
> under the 'pert test' framework. This script provides three testing
> scenarios:
...
> Below is detailed usage for it:
>
> # cd $linux/tools/perf -> This is important so can use shell script
> # perf test list
> [...]
> 70: probe libc's inet_pton & backtrace it with ping
> 71: Check Arm CoreSight trace data recording and synthesized samples
> 72: Check open filename arg using perf trace + vfs_getname
> 73: Zstd perf.data compression/decompression
> 74: Add vfs_getname probe to get syscall args filenames
> 75: Use vfs_getname probe to get syscall args filenames
>
> # perf test 71
> 71: Check Arm CoreSight trace data recording and branch samples: Ok
>
> Signed-off-by: Leo Yan <leo.yan@...aro.org>
Leo,
Thank you so much for testcase !
Reviewed-by: Suzuki K Poulose <suzuki.poulose@....com>
Powered by blists - more mailing lists