mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	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@kernel.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5] perf test: Introduce script for data symbol testing
Date: Thu, 6 Oct 2022 21:17:05 +0800	[thread overview]
Message-ID: <Yz7VUaXs0bhimqsP@leoy-yangtze.lan> (raw)
In-Reply-To: <Yz65kF01XYLayp9E@kernel.org>

On Thu, Oct 06, 2022 at 08:18:40AM -0300, Arnaldo Carvalho de Melo wrote:

[...]

> Replaced the one I had merged with v5 and added this:
> 
> Committer testing:
> 
>   [root@quaco ~]# grep -m1 "model name" /proc/cpuinfo
>   model name    : Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
>   [root@quaco ~]#
>   [root@quaco ~]# perf test -v "data symbol"
>   104: Test data symbol                                                :
>   --- start ---
>   test child forked, pid 192318
>   Compiling test program...
>   Recording workload...
>   [ perf record: Woken up 2 times to write data ]
>   [ perf record: Captured and wrote 0.389 MB /tmp/__perf_test.perf.data.LIuQl (5570 samples) ]
>   Cleaning up files...
>   test child finished with 0
>   ---- end ----
>   Test data symbol: Ok
>   [root@quaco ~]#
> 
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> -------------
> 
> The verbose mode could show the 'perf report' output, I think, but this
> can be done later, if agreed.

Yeah, will add output logs for the test.

Thanks for picking up patch.  And thanks for Ravi's testing.

Thanks,
Leo

  reply	other threads:[~2022-10-06 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 10:10 Leo Yan
2022-10-06 11:18 ` Arnaldo Carvalho de Melo
2022-10-06 13:17   ` Leo Yan [this message]
2022-10-06 11:34 ` Ravi Bangoria

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=Yz7VUaXs0bhimqsP@leoy-yangtze.lan \
    --to=leo.yan@linaro.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    /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®