From: Joe Korty <joe.korty@ccur.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make poll_idle behave more like the other idle methods
Date: Thu, 28 Aug 2008 11:19:40 -0400 [thread overview]
Message-ID: <20080828151940.GA21854@tsunami.ccur.com> (raw)
In-Reply-To: <20080828133335.GA1126@elte.hu>
On Thu, Aug 28, 2008 at 09:33:35AM -0400, Ingo Molnar wrote:
>> I saw the outer loop running continuously, from the old
>> trace patch which I had applied.
>
> ah - was that an older version of ftrace?
Believe it or not, it's a very old version of LTTng trace.
We have a guy that keeps dragging it forward (compatibility
reasons).
Joe
prev parent reply other threads:[~2008-08-28 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 14:35 [PATCH] make poll_idle behave more like the other idle methods Joe Korty
2008-08-28 9:00 ` Ingo Molnar
2008-08-28 10:40 ` Thomas Gleixner
2008-08-28 13:22 ` Joe Korty
2008-08-28 13:33 ` Ingo Molnar
2008-08-28 15:19 ` Joe Korty [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=20080828151940.GA21854@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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