From: Pawel Moll <pawel.moll@arm.com>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
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>,
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: [RFC 2/2] perf: Marker software event and ioctl
Date: Mon, 15 Sep 2014 18:18:37 +0100 [thread overview]
Message-ID: <1410801517.3817.13.camel@hornet> (raw)
In-Reply-To: <5415B790.5010607@gmail.com>
On Sun, 2014-09-14 at 16:43 +0100, David Ahern wrote:
> >> Seems really similar to what I proposed in the past:
Yeah, it wasn't really hard to come with similar conclusions :-)
> >> https://lkml.org/lkml/2011/2/27/159
> >>
> >> Which was rejected.
> >
> > I took a look at that thread, but just barely, emphasis on that.
> >
> > Injecting something from userspace, a la ftrace, seems to be something,
> > as tglx mentioned, "buried" in that patchset.
>
> Thomas object to an ioctl buried deep in a patch -- newbie mistake.
>
> Peter objected to the ioctl https://lkml.org/lkml/2011/3/1/229
>
> It was not userspace injecting random data into the stream but rather
> forcing the sample to be generated and added to the stream.
I would like to hear from Peter and others. If not here, I'll get them
to talk next month on Linux Plumbers :-)
Pawel
next prev parent reply other threads:[~2014-09-15 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 11:48 [RFC 0/2] Yet another take at user/kernel time correlation problem Pawel Moll
2014-09-12 11:48 ` [RFC 1/2] perf: Add sampling of the raw monotonic clock Pawel Moll
2014-09-12 11:48 ` [RFC 2/2] perf: Marker software event and ioctl Pawel Moll
2014-09-12 12:43 ` Christopher Covington
2014-09-12 12:57 ` Pawel Moll
2014-09-12 13:49 ` Arnaldo Carvalho de Melo
2014-09-12 13:58 ` Pawel Moll
2014-09-12 16:19 ` Arnaldo Carvalho de Melo
2014-09-15 17:27 ` Pawel Moll
2014-09-15 18:31 ` Arnaldo Carvalho de Melo
2014-09-16 16:33 ` Pawel Moll
2014-09-12 14:00 ` Christopher Covington
2014-09-12 17:37 ` David Ahern
2014-09-12 20:44 ` Arnaldo Carvalho de Melo
2014-09-14 15:43 ` David Ahern
2014-09-15 17:18 ` Pawel Moll [this message]
2014-09-16 7:44 ` Ingo Molnar
2014-09-16 16:37 ` Pawel Moll
2014-09-16 17:58 ` Ingo Molnar
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=1410801517.3817.13.camel@hornet \
--to=pawel.moll@arm.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--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
all inboxes | Powered by JetHome®