From: Steven Rostedt <rostedt@goodmis.org>
To: Will Hawkins <whh8b@virginia.edu>
Cc: Namhyung Kim <namhyung@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Ftrace vs perf user page fault statistics differences
Date: Wed, 14 Jun 2017 13:43:47 -0400 [thread overview]
Message-ID: <20170614134347.60063e88@gandalf.local.home> (raw)
In-Reply-To: <CAE+MWFt8csSJ9__FF27T+D8SOEGH41yL40z3SHmDeqM=G1DA4A@mail.gmail.com>
On Wed, 14 Jun 2017 13:30:59 -0400
Will Hawkins <whh8b@virginia.edu> wrote:
> > When perf profiles a program started by the same command line, it
> > disables the events by default and enables them during exec. Please
> > see linux/tools/perf/util/evsel.c:perf_evsel__config().
> >
> > Thanks,
> > Namhyung
>
> Namhyung,
>
> I think that this answers a very important question! Thanks for chiming in!
Yes. One difference between the design of ftrace and the design of
perf, is that, I avoided inserting call backs throughout the kernel.
Perf has a few function calls in the exec code. Just grep "perf" in
fs/exec.c. There's a few scattered around there. Causing a slight
overhead for when perf is not in use.
Hmm, I really should remove all perf injections and make them either a
tracepoint or generic jumplabels that anything may attach to. Then
ftrace could have the same features. And lttng for that matter.
-- Steve
prev parent reply other threads:[~2017-06-14 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 20:08 Will Hawkins
[not found] ` <CAE+MWFuvAtGc0boe3arhnyoVpCpJBOsBTpk8W7Lh6r5PFE-Hmg@mail.gmail.com>
2017-06-13 1:20 ` Steven Rostedt
2017-06-13 2:05 ` Will Hawkins
2017-06-13 13:06 ` Steven Rostedt
2017-06-13 18:02 ` Will Hawkins
2017-06-13 20:04 ` Steven Rostedt
2017-06-14 1:27 ` Will Hawkins
2017-06-14 2:13 ` Steven Rostedt
2017-06-14 17:47 ` Will Hawkins
2017-06-14 20:01 ` Steven Rostedt
2017-06-19 17:13 ` Will Hawkins
2017-06-19 18:52 ` Steven Rostedt
2017-06-14 3:04 ` Namhyung Kim
2017-06-14 17:30 ` Will Hawkins
2017-06-14 17:43 ` Steven Rostedt [this message]
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=20170614134347.60063e88@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=whh8b@virginia.edu \
/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®