From: Ingo Molnar <mingo@kernel.org>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
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-kernel@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] perf: Userspace event
Date: Fri, 26 Sep 2014 13:24:24 +0200 [thread overview]
Message-ID: <20140926112424.GC9870@gmail.com> (raw)
In-Reply-To: <1411729190.3852.21.camel@hornet>
* Pawel Moll <pawel.moll@arm.com> wrote:
> On Fri, 2014-09-26 at 07:21 +0100, Namhyung Kim wrote:
>
> > It looks like what trace-marker in ftrace does.. We might
> > connect output of the trace marker into a perf event somehow.
>
> I can probably trace_marker's write handler do the same as the
> new prctl() would do. [...]
Please keep this new facility separate, so that !ftrace kernels
that have perf events enabled still have this facility, etc.
Thanks,
Ingo
next prev parent reply other threads:[~2014-09-26 11:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 17:03 [PATCH v2 0/2] perf: User/kernel time correlation and event generation Pawel Moll
2014-09-23 17:03 ` [PATCH v2 1/2] perf: Add sampling of the raw monotonic clock Pawel Moll
2014-09-24 5:41 ` Namhyung Kim
2014-09-25 10:49 ` Pawel Moll
2014-09-26 6:16 ` Namhyung Kim
2014-09-26 10:58 ` Pawel Moll
2014-09-26 14:38 ` Namhyung Kim
2014-09-26 15:05 ` Pawel Moll
2014-09-26 19:25 ` David Ahern
2014-09-29 14:47 ` Pawel Moll
2014-09-23 17:03 ` [PATCH v2 2/2] perf: Userspace event Pawel Moll
2014-09-24 6:07 ` Namhyung Kim
2014-09-24 7:20 ` Ingo Molnar
2014-09-26 6:21 ` Namhyung Kim
2014-09-26 10:59 ` Pawel Moll
2014-09-26 11:24 ` Ingo Molnar [this message]
2014-09-25 12:45 ` Pawel Moll
2014-09-26 6:23 ` Namhyung Kim
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=20140926112424.GC9870@gmail.com \
--to=mingo@kernel.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=namhyung@kernel.org \
--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
Powered by JetHome