public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 0/2] perf: User/kernel time correlation and event generation
Date: Thu, 18 Sep 2014 11:02:35 -0400	[thread overview]
Message-ID: <541AF40B.7070604@codeaurora.org> (raw)
In-Reply-To: <1411050873-9310-1-git-send-email-pawel.moll@arm.com>

Hi Pawel,

On 09/18/2014 10:34 AM, Pawel Moll wrote:
> Greetings,
> 
> This is a second spin of the short series posted last week:
> 
> http://www.spinics.net/lists/kernel/msg1824419.html
> 
> The first patch adds an additional timestamp field in the perf
> sample data, which can be requested for any perf event along
> with normal PERF_SAMPLE_TIME. Events with both values appearing
> periodically in the perf data allow user code to translate
> raw monotonic time (obtained via POSIX clock API) to sched_clock
> domain. Although any perf event can be used, the natural choice
> would be a sched_switch trace event (for processes with root
> permissions) or a hrtimer-based PERF_COUNT_SW_CPU_CLOCK.
> 
> It didn't attract any comments previously, so is just re-posted
> without any changes.
> 
> The second patch, functionally orthogonal but complementing
> the first one, builds on the ftrace "trace_maker" idea. It adds
> a ioctl that can be used to inject a userspace-generated data
> into the perf buffer. It provides base for printf-like
> functionality in perf world. If used with the previous patch,
> it can be also used to provide synchronisation points for sched
> vs. raw monotonic time stamps correlation.
> 
> First version of the patch was taking a zero-terminated string
> as an argument. Now it is taking a custom structure with "type"
> and "size" integer fields followed by data. Type value "0"
> is defined as a zero-terminated string (although size, including
> the NULL character, must still be provided), but meaning of data
> for other types is of no interest for the kernel. The intention
> is to host a list of "well known" types (with reference parsers
> for them) in the user perf tool code.

Would it be possible for you to also update the corresponding man pages?

https://www.kernel.org/doc/man-pages/

Thanks,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

  parent reply	other threads:[~2014-09-18 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 14:34 [PATCH 0/2] perf: User/kernel time correlation and event generation Pawel Moll
2014-09-18 14:34 ` [PATCH 1/2] perf: Add sampling of the raw monotonic clock Pawel Moll
2014-09-29 15:28   ` Peter Zijlstra
2014-09-29 15:45     ` Pawel Moll
2014-09-18 14:34 ` [PATCH 2/2] perf: Userspace software event and ioctl Pawel Moll
2014-09-23 17:02   ` Pawel Moll
2014-09-24  7:49     ` Ingo Molnar
2014-09-25 17:20       ` Pawel Moll
2014-09-25 18:33         ` Ingo Molnar
2014-09-26 10:48           ` Pawel Moll
2014-09-26 11:23             ` Ingo Molnar
2014-09-26 11:26               ` Pawel Moll
2014-09-26 11:31                 ` Ingo Molnar
2014-09-27 17:14           ` Frederic Weisbecker
2014-09-29 14:52             ` Pawel Moll
2014-09-29 15:32   ` Peter Zijlstra
2014-09-29 15:53     ` Pawel Moll
2014-11-03 14:48       ` Tomeu Vizoso
2014-11-03 15:04         ` Pawel Moll
2014-09-18 15:02 ` Christopher Covington [this message]
2014-09-18 15:07   ` [PATCH 0/2] perf: User/kernel time correlation and event generation Pawel Moll
2014-09-18 15:48     ` Christopher Covington

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=541AF40B.7070604@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=acme@kernel.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtk.manpages@gmail.com \
    --cc=paulus@samba.org \
    --cc=pawel.moll@arm.com \
    --cc=peterz@infradead.org \
    --cc=richardcochran@gmail.com \
    --cc=rostedt@goodmis.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