All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
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>,
	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 14:43:05 +0300	[thread overview]
Message-ID: <87149798-6031-9ca1-5725-3f6e4b428946@linux.intel.com> (raw)
In-Reply-To: <20181009193202.GE10775@kernel.org>

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?

Thanks,
Alexey

  reply	other threads:[~2018-10-23 11:43 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 [this message]
2018-10-23 13:17     ` Arnaldo Carvalho de Melo
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=87149798-6031-9ca1-5725-3f6e4b428946@linux.intel.com \
    --to=alexey.budankov@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@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 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.