From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v7 2/6] perf record: Get the first sample time and last sample time
Date: Sat, 6 Jan 2018 06:55:56 +0800 [thread overview]
Message-ID: <65a7172d-7e19-faec-d7c6-5384fc9d5b20@linux.intel.com> (raw)
In-Reply-To: <20180105125341.GA25476@kernel.org>
On 1/5/2018 8:53 PM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jan 05, 2018 at 09:15:03AM +0800, Jin, Yao escreveu:
>>
>>
>> On 1/5/2018 3:09 AM, Arnaldo Carvalho de Melo wrote:
>>> Em Fri, Dec 08, 2017 at 09:13:42PM +0800, Jin Yao escreveu:
>>>> In the default 'perf record' configuration, all samples are processed,
>>>> to create the HEADER_BUILD_ID table. So it's very easy to get the
>>>> first/last samples and save the time to perf file header via the
>>>> function write_sample_time().
>>>>
>>>> Later, at post processing time, perf report/script will fetch
>>>> the time from perf file header.
>>>
>>> So, at this point I was expecting that that record would be present on
>>> the perf.data file:
>>>
>>> [acme@jouet perf]$ perf record --timestamp-boundary sleep 1
>>> Cannot read kernel map
>>> [ perf record: Woken up 1 times to write data ]
>>> [ perf record: Captured and wrote 0.001 MB perf.data (7 samples) ]
>>> [acme@jouet perf]$ perf report -D | grep PERF_RECORD_SAMPLE | wc -l
>>> 7
>>> [acme@jouet perf]$ perf report -D | grep PERF_RECORD_SAMPLE_TIME
>>> [acme@jouet perf]$
>>>
>>> What am I doing wrong?
>>>
>>> To clarify, this is with just the first two patches in this series
>>> applied.
>>>
>>> - Arnaldo
>>
>> Hi Arnaldo,
>>
>> The timestamp boundary information is saved in perf file header.
>
> Right, my bad, I somehow thought it would be as PERF_RECORD_SAMPLE_TIME,
> duh.
>
> Will continue reviewing, sorry about that.
>
> - Arnaldo
>
Thanks for reviewing the patch.
If you see anything I should improve, please let me know.
Thanks
Jin Yao
>> So if we want to look at them, we need to add '--header' in perf report.
>>
>> For example,
>>
>> root@skl:/tmp# perf report -D --header | grep 'time of'
>> # time of first sample : 248333.706656
>> # time of last sample : 248357.215328
>>
>> Thanks
>> Jin Yao
next prev parent reply other threads:[~2018-01-05 22:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 13:13 [PATCH v7 0/6] perf report/script: Support percent and multiple range in --time option Jin Yao
2017-12-08 13:13 ` [PATCH v7 1/6] perf header: Record first sample time and last sample time in perf file header Jin Yao
2018-01-11 6:21 ` [tip:perf/core] perf header: Add infrastructure to record first and last sample time tip-bot for Jin Yao
2017-12-08 13:13 ` [PATCH v7 2/6] perf record: Get the first sample time " Jin Yao
2018-01-04 19:09 ` Arnaldo Carvalho de Melo
2018-01-05 1:15 ` Jin, Yao
2018-01-05 12:53 ` Arnaldo Carvalho de Melo
2018-01-05 22:55 ` Jin, Yao [this message]
2018-01-11 6:22 ` [tip:perf/core] perf record: Record the first and last sample time in the header tip-bot for Jin Yao
2017-12-08 13:13 ` [PATCH v7 3/6] perf util: Create function to parse time percent Jin Yao
2018-01-08 14:31 ` Arnaldo Carvalho de Melo
2018-01-08 14:38 ` Arnaldo Carvalho de Melo
2018-01-09 1:18 ` Jin, Yao
2018-01-11 6:22 ` [tip:perf/core] perf tools: " tip-bot for Jin Yao
2017-12-08 13:13 ` [PATCH v7 4/6] perf util: Create function to perform multiple time range checking Jin Yao
2018-01-11 6:22 ` [tip:perf/core] perf tools: " tip-bot for Jin Yao
2017-12-08 13:13 ` [PATCH v7 5/6] perf report: support time percent and multiple time ranges Jin Yao
2018-01-08 14:45 ` Arnaldo Carvalho de Melo
2018-01-08 14:48 ` Arnaldo Carvalho de Melo
2018-01-08 14:53 ` Arnaldo Carvalho de Melo
2018-01-08 15:02 ` Arnaldo Carvalho de Melo
2018-01-08 15:04 ` Arnaldo Carvalho de Melo
2018-01-09 2:02 ` Jin, Yao
2018-01-11 6:23 ` [tip:perf/core] perf report: Support " tip-bot for Jin Yao
2017-12-08 13:13 ` [PATCH v7 6/6] perf script: support " Jin Yao
2018-01-11 6:23 ` [tip:perf/core] perf script: Support " tip-bot for Jin Yao
2017-12-13 14:28 ` [PATCH v7 0/6] perf report/script: Support percent and multiple range in --time option Arnaldo Carvalho de Melo
2017-12-14 0:48 ` Jin, Yao
2017-12-14 14:08 ` Jiri Olsa
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=65a7172d-7e19-faec-d7c6-5384fc9d5b20@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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
Powered by JetHome