From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Jiri Olsa" <jolsa@kernel.org>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"David Ahern" <dsahern@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Michael Petlan" <mpetlan@redhat.com>,
"Ian Rogers" <irogers@google.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Geneviève Bastien" <gbastien@versatic.net>,
"Wang Nan" <wangnan0@huawei.com>,
"Jeremie Galarneau" <jgalar@efficios.com>
Subject: Re: [PATCH 2/6] perf tools: Store clock references for -k/--clockid option
Date: Mon, 3 Aug 2020 13:35:59 +0200 [thread overview]
Message-ID: <20200803113559.GE139381@krava> (raw)
In-Reply-To: <20200803035550.GA686281@google.com>
On Mon, Aug 03, 2020 at 12:55:50PM +0900, Namhyung Kim wrote:
SNIP
> > diff --git a/tools/perf/Documentation/perf.data-file-format.txt b/tools/perf/Documentation/perf.data-file-format.txt
> > index b6472e463284..c484e81987c7 100644
> > --- a/tools/perf/Documentation/perf.data-file-format.txt
> > +++ b/tools/perf/Documentation/perf.data-file-format.txt
> > @@ -389,6 +389,19 @@ struct {
> > Example:
> > cpu pmu capabilities: branches=32, max_precise=3, pmu_name=icelake
> >
> > + HEADER_CLOCK_DATA = 29,
> > +
> > + Contains clock id and its reference time together with wall clock
> > + time taken at the 'same time', both values are in nanoseconds.
> > + The format of data is as below.
> > +
> > +struct {
> > + u32 version; /* version = 1 */
> > + u32 clockid;
> > + u64 clockid_time_ns;
> > + u64 wall_clock_ns;
> > +};
> > +
>
> It seems that it's slightly different than what it actually write to a file.
> Specifically the last two fields should be reversed IMHO.
oops, you're right.. wil fix in new version
>
>
> > other bits are reserved and should ignored for now
> > HEADER_FEAT_BITS = 256,
> >
> [SNIP]
>
> > diff --git a/tools/perf/util/env.h b/tools/perf/util/env.h
> > index 1ab2682d5d2b..4098a63d5e64 100644
> > --- a/tools/perf/util/env.h
> > +++ b/tools/perf/util/env.h
> > @@ -100,6 +100,18 @@ struct perf_env {
> > /* For fast cpu to numa node lookup via perf_env__numa_node */
> > int *numa_map;
> > int nr_numa_map;
> > +
> > + /* For real clock time refference. */
>
> typo: reference
ok
SNIP
> > + else {
> > + strftime(date, sizeof(date), "%F %T", <ime);
> > + scnprintf(tstr, sizeof(tstr), "%s.%06d",
> > + date, (int) tod_ns.tv_usec);
> > + }
> > +
> > + fprintf(fp, "# clockid: %s (%u)\n", clockid_name(clockid), clockid);
> > + fprintf(fp, "# reference time: %s = %ld.%06d (TOD) = %ld.%ld (%s)\n",
>
> Shouldn't the last one be %ld.%09ld?
sure, why not
thanks,
jirka
next prev parent reply other threads:[~2020-08-03 11:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 21:39 [PATCH 0/6] perf tools: Add wallclock time conversion support Jiri Olsa
2020-07-30 21:39 ` [PATCH 1/6] perf tools: Add clockid_name function Jiri Olsa
2020-07-31 15:33 ` Andi Kleen
2020-07-31 16:19 ` Jiri Olsa
2020-07-30 21:39 ` [PATCH 2/6] perf tools: Store clock references for -k/--clockid option Jiri Olsa
2020-07-31 15:52 ` Alexey Budankov
2020-07-31 16:15 ` Jiri Olsa
2020-07-31 16:35 ` David Ahern
2020-08-03 3:55 ` Namhyung Kim
2020-08-03 11:35 ` Jiri Olsa [this message]
2020-07-30 21:39 ` [PATCH 3/6] perf tools: Move clockid_res_ns under clock struct Jiri Olsa
2020-07-30 21:39 ` [PATCH 4/6] perf tools: Add support to store time of day in CTF data conversion Jiri Olsa
2020-08-03 4:00 ` Namhyung Kim
2020-08-03 11:31 ` Jiri Olsa
2020-07-30 21:39 ` [PATCH 5/6] perf script: Change enum perf_output_field values to be 64 bits Jiri Olsa
2020-07-30 21:39 ` [PATCH 6/6] perf script: Add tod field to display time of day Jiri Olsa
2020-07-30 22:14 ` [PATCH 0/6] perf tools: Add wallclock time conversion support peterz
2020-07-31 1:21 ` David Ahern
2020-07-31 7:47 ` Jiri Olsa
2020-07-31 15:36 ` Andi Kleen
2020-07-31 18:05 ` peterz
2020-08-01 0:46 ` David Ahern
2020-08-01 17:49 ` Arnaldo Carvalho de Melo
2020-07-31 17:20 ` peterz
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=20200803113559.GE139381@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=gbastien@versatic.net \
--cc=irogers@google.com \
--cc=jgalar@efficios.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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