From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tracing/function-graph-tracer: prevent from hrtimer interrupt infinite loop
Date: Thu, 18 Dec 2008 12:16:12 +0100 [thread overview]
Message-ID: <20081218111612.GD14332@elte.hu> (raw)
In-Reply-To: <c62985530812180251k7fde4f13tce5118a3eac4975b@mail.gmail.com>
* Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 2008/12/18 Ingo Molnar <mingo@elte.hu>:
> >
> > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> >
> >> Impact: fix a system hang on slow systems
> >>
> >> While testing the function graph tracer on VirtualBox, I had a system hang
> >> immediatly after enabling the tracer.
> >>
> >> If hrtimer is enabled on kernel, a slow system can spend too much time
> >> during tracing the hrtimer_interrupt which will do eternal loops,
> >> assuming it always have to retry its process because too much time
> >> elapsed during its time update. Now we provide a feature which lurks at
> >> the number of retries on hrtimer_interrupt. After 10 retries, the
> >> function graph tracer will definetly stop its tracing.
> >
> > hm, i dont really like this solution - it just works around the problem by
> > 'speeding up' the system. If we have a _real_ slow system, there's no such
> > way for us to speed it up.
>
>
> It doesn' speed up the system actually. That's not the goal of this
> patch.
i meant that abstractly. The "solution" here is that your patch turns off
the function-graph-tracer. The practical effect of that is: the system
gets much faster at processing hrtimer IRQs and effectively "speeds up".
ok?
Ingo
prev parent reply other threads:[~2008-12-18 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 1:09 [PATCH v2] tracing/function-graph-tracer: prevent from hrtimer interrupt infinite loop Frederic Weisbecker
2008-12-18 10:34 ` Ingo Molnar
2008-12-18 10:48 ` Thomas Gleixner
2008-12-18 10:56 ` Frédéric Weisbecker
2008-12-18 11:22 ` Ingo Molnar
2008-12-18 21:07 ` Frédéric Weisbecker
2008-12-18 21:16 ` Ingo Molnar
2008-12-18 21:36 ` Frédéric Weisbecker
2008-12-18 21:44 ` Ingo Molnar
2008-12-18 22:00 ` Frédéric Weisbecker
2008-12-21 10:00 ` Ingo Molnar
2008-12-21 10:12 ` Ingo Molnar
2008-12-21 12:21 ` Frédéric Weisbecker
2008-12-22 10:46 ` Frédéric Weisbecker
2008-12-18 10:51 ` Frédéric Weisbecker
2008-12-18 11:16 ` Ingo Molnar [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=20081218111612.GD14332@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.