From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: leo.yan@linaro.org, acme@kernel.org, mathieu.poirier@linaro.org,
mike.leach@linaro.org, peterz@infradead.org, mingo@redhat.com,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] perf test: Introduce script for Arm CoreSight testing
Date: Mon, 7 Sep 2020 15:10:37 +0100 [thread overview]
Message-ID: <6333f002-1213-0e20-0fcc-b3bfc0723b97@arm.com> (raw)
In-Reply-To: <20200907130154.9601-1-leo.yan@linaro.org>
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@linaro.org>
Leo,
Thank you so much for testcase !
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
next prev parent reply other threads:[~2020-09-07 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 13:01 Leo Yan
2020-09-07 14:10 ` Suzuki K Poulose [this message]
2020-09-08 19:12 ` Mathieu Poirier
2020-09-10 12:10 ` Arnaldo Carvalho de Melo
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=6333f002-1213-0e20-0fcc-b3bfc0723b97@arm.com \
--to=suzuki.poulose@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.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=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®