From: Johannes Weiner <hannes@cmpxchg.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] trace: funcgraph tracer - adding funcgraph-irq option
Date: Thu, 9 Sep 2010 16:44:30 +0200 [thread overview]
Message-ID: <20100909144430.GG20955@cmpxchg.org> (raw)
In-Reply-To: <1283876920.5133.125.camel@gandalf.stny.rr.com>
Hi Guys,
On Tue, Sep 07, 2010 at 12:28:40PM -0400, Steven Rostedt wrote:
> On Fri, 2010-07-23 at 15:19 +0200, Jiri Olsa wrote:
> > On Thu, Jul 22, 2010 at 04:00:21PM -0400, Steven Rostedt wrote:
> > > On Mon, 2010-07-12 at 18:21 +0200, Jiri Olsa wrote:
> > >
> > SNIP
> >
> > >
> > > What happens if we lose the return event? That is, due to buffer
> > > overruns, the return of the trace is lost. Then we lose out on all
> > > events until another event of the same IRQ happens and its return is not
> > > lost.
> > >
> > > You should save the depth instead of the function. When you are in a
> > > interrupt, record the depth. Then when the depth is less than or equal
> > > to the recorded depth you can restart printing. This may still suffer
> > > from missed returns, but it would not have as much of a consequence when
> > > it happens.
> > hi,
> > you're right, changed patch is attached
> >
> > thanks,
> > jirka
> >
> > ---
> > Adding funcgraph-irq option for function graph tracer.
> >
> > It's handy to be able to disable the irq related output
> > and not to have to jump over each irq related code, when
> > you have no interrest in it.
Although greatly reduced, I still see the following noise in the trace
output with the IRQ filtering enabled:
1) | wakeup_flusher_threads() {
1) 0.205 us | __rcu_read_lock();
1) 0.271 us | bdi_has_dirty_io();
1) 0.287 us | bdi_has_dirty_io();
1) 0.217 us | bdi_has_dirty_io();
1) | bdi_has_dirty_io() {
1) | smp_invalidate_interrupt() {
1) 0.220 us | native_apic_mem_write();
1) 0.794 us | } /* smp_invalidate_interrupt */
1) 1.413 us | } /* bdi_has_dirty_io */
1) 0.218 us | bdi_has_dirty_io();
1) 0.213 us | bdi_has_dirty_io();
1) 0.215 us | bdi_has_dirty_io();
1) | smp_invalidate_interrupt() {
1) 0.234 us | native_apic_mem_write();
1) 0.819 us | } /* smp_invalidate_interrupt */
1) 0.240 us | bdi_has_dirty_io();
1) 0.259 us | bdi_has_dirty_io();
next prev parent reply other threads:[~2010-09-09 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 16:21 [PATCH] trace: funcgraph tracer - adding funcgraph-irq option Jiri Olsa
2010-07-22 20:00 ` Steven Rostedt
2010-07-23 13:19 ` [PATCHv2] " Jiri Olsa
[not found] ` <20100907113102.GA1912@jolsa.brq.redhat.com>
[not found] ` <1283867057.5133.75.camel@gandalf.stny.rr.com>
2010-09-07 14:53 ` Jiri Olsa
2010-09-15 8:41 ` [tip:perf/core] tracing: Add funcgraph-irq option for function graph tracer tip-bot for Jiri Olsa
2010-09-07 16:28 ` [PATCHv2] trace: funcgraph tracer - adding funcgraph-irq option Steven Rostedt
2010-09-07 17:19 ` Johannes Weiner
2010-09-09 14:44 ` Johannes Weiner [this message]
2010-09-09 18:10 ` Jiri Olsa
2010-09-11 1:18 ` Steven Rostedt
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=20100909144430.GG20955@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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