mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] ftrace / perf 'recursion'
Date: Wed, 17 Aug 2016 11:04:48 -0400	[thread overview]
Message-ID: <20160817110448.20b4a6db@gandalf.local.home> (raw)
In-Reply-To: <20160817145709.GS30192@twins.programming.kicks-ass.net>

On Wed, 17 Aug 2016 16:57:09 +0200
Peter Zijlstra <peterz@infradead.org> wrote:


> We'd still need the irq_work to wake tasks stuck in poll() and friends.
> And once we're over the watermark, every new event will trigger that
> wakeup, and the wakeup will generate a new event etc..

I just byte the bullet for those (first OS world) issues. If one wants
to trace wake ups, and the wake up of the trace task gets traced, which
causes the trace task to wake up more often, and add more events, then
so be it. I like to see how the tracer affects the system as well. I
noticed that hiding the tracer can make it confusing if one sees gaps
in the trace, where it was the tracer causing it.

-- Steve

      reply	other threads:[~2016-08-17 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  9:19 Peter Zijlstra
2016-08-17 10:33 ` Peter Zijlstra
2016-08-17 10:57   ` Peter Zijlstra
2016-08-17 13:49     ` Steven Rostedt
2016-08-17 14:06       ` Peter Zijlstra
2016-08-17 14:25         ` Steven Rostedt
2016-08-17 14:57           ` Peter Zijlstra
2016-08-17 15:04             ` 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=20160817110448.20b4a6db@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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®