From: Pawel Moll <pawel.moll@arm.com>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ron Rechenmacher <ron@fnal.gov>,
Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] tracing: Export key trace event symbols
Date: Thu, 23 Apr 2015 16:33:42 +0100 [thread overview]
Message-ID: <1429803222.3242.24.camel@arm.com> (raw)
In-Reply-To: <1429802909.3242.23.camel@arm.com>
On Thu, 2015-04-23 at 16:28 +0100, Pawel Moll wrote:
> On Wed, 2015-04-22 at 16:36 +0100, David Ahern wrote:
> > On 4/22/15 8:47 AM, Arnaldo Carvalho de Melo wrote:
> > > Em Wed, Apr 22, 2015 at 08:53:14AM -0400, Steven Rostedt escreveu:
> > >> >On Tue, 21 Apr 2015 21:24:51 -0500
> > >> >Ron Rechenmacher<ron@fnal.gov> wrote:
> > >>> > >I've looked at the above reference briefly and it appears that user-space
> > >>> > >would be mmapping the buffer read-only. Is that correct?
> > >> >
> > >> >Correct, but I'm sure we could still add something (if it doesn't
> > >> >already exist) to have userspace write into the buffer. Ftrace has that
> > >> >with the trace_marker file.
> > > There is something in the works, I guess Pawell Moll (sp) was working on it, and
> > > David Ahern (CCed) should know, David?
> > >
> >
> > I played around with generating perf events in userspace with the
> > intention of having the userspace events get merged with kernel events
> > during the processing stage, but I did not take it to the point of
> > integrating into perf. This was around October 2013. I got distracted
> > with other topics and have not come back to it.
> >
> > Pawel has a patch that allows userspace to inject events into the stream
> > via ioctl calls.
>
> In the last version it was even a prctl - no need for a perf file
> descriptor any more :-)
>
> But the patch requires more care if it's to go in, so I'm open to people
> screaming "yes, we need it!" ;-)
Forgot to quote the link:
http://article.gmane.org/gmane.linux.kernel.api/5851
Pawel
next prev parent reply other threads:[~2015-04-23 15:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:38 [PATCH] tracing: Export key trace event symbols Ron Rechenmacher
2015-04-21 6:10 ` Christoph Hellwig
2015-04-21 12:04 ` Ron Rechenmacher
2015-04-21 12:19 ` Ron Rechenmacher
2015-04-21 13:38 ` Steven Rostedt
2015-04-21 12:22 ` Christoph Hellwig
2015-04-21 13:13 ` Ron Rechenmacher
2015-04-21 13:23 ` Christoph Hellwig
2015-04-21 13:26 ` Ron Rechenmacher
2015-04-21 13:53 ` Steven Rostedt
2015-04-21 15:00 ` Ron Rechenmacher
2015-04-21 15:49 ` Steven Rostedt
2015-04-21 22:23 ` Ron Rechenmacher
2015-04-21 22:44 ` Steven Rostedt
2015-04-22 2:24 ` Ron Rechenmacher
2015-04-22 12:53 ` Steven Rostedt
2015-04-22 12:55 ` Steven Rostedt
2015-04-22 14:47 ` Arnaldo Carvalho de Melo
2015-04-22 15:36 ` David Ahern
2015-04-22 15:44 ` Steven Rostedt
2015-04-22 16:35 ` Ron Rechenmacher
2015-04-22 17:00 ` Steven Rostedt
2015-04-23 15:28 ` Pawel Moll
2015-04-23 15:33 ` Pawel Moll [this message]
2015-04-21 13:31 ` Steven Rostedt
2015-04-24 21:24 ` Steven Rostedt
2015-04-24 21:39 ` Mathieu Desnoyers
2015-04-27 19:12 ` Ron Rechenmacher
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=1429803222.3242.24.camel@arm.com \
--to=pawel.moll@arm.com \
--cc=arjan@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ron@fnal.gov \
--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;
as well as URLs for NNTP newsgroup(s).