From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki Poulouse <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Basil Eljuse <Basil.Eljuse@arm.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] perf test: Output sub testing result in cs-etm
Date: Thu, 18 Feb 2021 16:30:52 -0300 [thread overview]
Message-ID: <YC7AbM4fPBs7DxVo@kernel.org> (raw)
In-Reply-To: <20210215115944.535986-1-leo.yan@linaro.org>
Em Mon, Feb 15, 2021 at 07:59:42PM +0800, Leo Yan escreveu:
> The "perf test" can be integrated into testing framework, e.g. Linux
> kernel functional testing (LKFT) [1]. We are not satisfied with only
> outputting the summarized result for Arm CoreSight testing but lacking
> more detailed result for sub testing.
>
> This patch set is to output sub testing result in cs-etm. Thus the
> testing framework can extract the detailed info and generates reports
> for which sub cases causes failure.
>
> This patch set is cleanly applied on perf/core branch with:
>
> commit 6db59d357e8e ("perf arm64/s390: Fix printf conversion specifier for IP addresses")
>
> After applied the patches, which is tested on Arm Juno-r2 board with
> option '-v', the output result is shown in below; the introduced sub
> testing result has the format like:
Thanks, applied.
- Arnaldo
> "CoreSight path testing (CPU0 -> tmc_etf0): PASS".
>
>
> # perf test 73 -v
> 73: Check Arm CoreSight trace data recording and synthesized samples:
> --- start ---
> test child forked, pid 17423
> Recording trace (only user mode) with path: CPU0 => tmc_etf0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU0 -> tmc_etf0): PASS
> Recording trace (only user mode) with path: CPU0 => tmc_etr0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU0 -> tmc_etr0): PASS
> Recording trace (only user mode) with path: CPU1 => tmc_etf0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU1 -> tmc_etf0): PASS
> Recording trace (only user mode) with path: CPU1 => tmc_etr0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU1 -> tmc_etr0): PASS
> Recording trace (only user mode) with path: CPU2 => tmc_etf0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU2 -> tmc_etf0): PASS
> Recording trace (only user mode) with path: CPU2 => tmc_etr0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU2 -> tmc_etr0): PASS
> Recording trace (only user mode) with path: CPU3 => tmc_etf0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU3 -> tmc_etf0): PASS
> Recording trace (only user mode) with path: CPU3 => tmc_etr0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU3 -> tmc_etr0): PASS
> Recording trace (only user mode) with path: CPU4 => tmc_etf0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU4 -> tmc_etf0): PASS
> Recording trace (only user mode) with path: CPU4 => tmc_etr0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU4 -> tmc_etr0): PASS
> Recording trace (only user mode) with path: CPU5 => tmc_etf0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU5 -> tmc_etf0): PASS
> Recording trace (only user mode) with path: CPU5 => tmc_etr0
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight path testing (CPU5 -> tmc_etr0): PASS
> Recording trace with system wide mode
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight system wide testing: PASS
> Recording trace with snapshot mode
> Looking at perf.data file for dumping branch samples:
> Looking at perf.data file for reporting branch samples:
> Looking at perf.data file for instruction samples:
> CoreSight snapshot testing: PASS
> test child finished with 0
> ---- end ----
> Check Arm CoreSight trace data recording and synthesized samples: Ok
>
> [1] https://lkft.linaro.org/
>
>
> Leo Yan (2):
> perf test: Suppress logs in cs-etm testing
> perf test: Output the sub testing result in cs-etm
>
> tools/perf/tests/shell/test_arm_coresight.sh | 45 ++++++++++----------
> 1 file changed, 23 insertions(+), 22 deletions(-)
>
> --
> 2.25.1
>
--
- Arnaldo
prev parent reply other threads:[~2021-02-18 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 11:59 [PATCH v1 0/2] perf test: Output sub testing result in cs-etm Leo Yan
2021-02-15 11:59 ` [PATCH v1 1/2] perf test: Suppress logs in cs-etm testing Leo Yan
2021-02-15 11:59 ` [PATCH v1 2/2] perf test: Output the sub testing result in cs-etm Leo Yan
2021-02-18 19:30 ` Arnaldo Carvalho de Melo [this message]
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=YC7AbM4fPBs7DxVo@kernel.org \
--to=acme@kernel.org \
--cc=Basil.Eljuse@arm.com \
--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=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=viresh.kumar@linaro.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 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.