From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] perf record: encode -k clockid frequency into Perf trace
Date: Tue, 23 Oct 2018 10:17:07 -0300 [thread overview]
Message-ID: <20181023131707.GA3657@kernel.org> (raw)
In-Reply-To: <87149798-6031-9ca1-5725-3f6e4b428946@linux.intel.com>
Em Tue, Oct 23, 2018 at 02:43:05PM +0300, Alexey Budankov escreveu:
> Hi Arnaldo,
>
> On 09.10.2018 22:32, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Oct 09, 2018 at 05:36:24PM +0300, Alexey Budankov escreveu:
> >>
> >> Store -k clockid frequency into Perf trace to enable timestamps
> >> derived metrics conversion into wall clock time on reporting stage.
> >>
> >> Below is the example of perf report output:
> >
> > Applied, building, lets see this time.
>
> Thanks for the effort. So far I assume the outstanding issues
> were addressed. Is the patch still planned for coming release?
yep, its in my perf/core branch:
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=cf7905165fee15fe26ac4a91ee0a35b966249430
I'll process some more patches from Adrian and Andi today, both making
use of Intel Xed, that seems to be installed ok now in my test machines,
and then send a pull req to Ingo,
Thanks,
- Arnaldo
next prev parent reply other threads:[~2018-10-23 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 14:36 [PATCH v5] perf record: encode -k clockid frequency into Perf trace Alexey Budankov
2018-10-09 19:32 ` Arnaldo Carvalho de Melo
2018-10-23 11:43 ` Alexey Budankov
2018-10-23 13:17 ` Arnaldo Carvalho de Melo [this message]
2018-10-26 7:27 ` [tip:perf/urgent] perf record: Encode " tip-bot for Alexey Budankov
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=20181023131707.GA3657@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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