From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>
Subject: Re: [PATCH 0/6] [git pull] updates for tip/tracing/ftrace
Date: Wed, 18 Feb 2009 19:19:26 +0100 [thread overview]
Message-ID: <20090218181926.GA26802@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0902181203470.11411@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> [ Note, I upgrade my email server which caused a bit of havoc, I'm
> just getting emails back from yesterday ]
>
>
> On Wed, 18 Feb 2009, Ingo Molnar wrote:
>
> >
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> > > it's one of these recent commits:
> > >
> > > fa7c7f6: tracing/core: remove unused parameter in tracing_fill_pipe_page()
> > > 6eaaa5d: tracing/core: use appropriate waiting on trace_pipe
> > > 35ebf1c: ftrace: show unlimited when traceon or traceoff has no counter
> > > 73d8b8b: tracing: fix typing mistake in hint message and comments
> > > d2ef7c2: tracing: fix the return value of trace selftest
> > > af51309: tracing: use the more proper parameter
> > > b6887d7: ftrace: rename _hook to _probe
> > > 6a24a24: ftrace: clean up coding style
> > >
> > > Have not bisected it any further, excluded them from
> > > tip:master for the time being.
> >
> > actually - it's one of these:
> >
> > 37bd824: Merge branches 'tracing/ftrace' and 'tracing/urgent' into tracing/core
> > 5b058bc: tracing/function-graph-tracer: trace the idle tasks
> > 73d3fd9: ftrace: fix !CONFIG_DYNAMIC_FTRACE ftrace_swapper_pid definition
> > 97d0bb8: ftrace: fix !CONFIG_FTRACE [un_]register_ftrace_command() prototypes
> > f492d3f8: Merge branch 'tip/tracing/ftrace' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace into tracing/ftrace
> > c4e2b43: Merge branches 'tracing/hw-branch-tracing' and 'tracing/power-tracer' into tracing/core
> > e110e3d: ftrace: add pretty print function for traceon and traceoff hooks
> > 809dcf2: ftrace: add pretty print to selected fuction traces
> > 8fc0c70: ftrace: show selected functions in set_ftrace_filter
> > 23b4ff3: ftrace: add traceon traceoff commands to enable/disable the buffers
> > 988ae9d: ring-buffer: add tracing_is_on to test if ring buffer is enabled
> > 59df055: ftrace: trace different functions with a different tracer
> > e6ea44e: ftrace: consolidate mutexes
>
> The above consolidate mutexs would be a prime suspect for a hard lockup.
> It may very well be that. When I finally receive your config, I'll give it
> a test. I saw you post the config by looking a web archive, but my email
> server is still in the processes of retrieving all my email from the last
> day or so.
here's a clickable link:
http://redhat.com/~mingo/misc/config-ftrace-breakage-2009-02-18
ngo
next prev parent reply other threads:[~2009-02-18 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 18:20 [PATCH 0/6] [git pull] updates for tip/tracing/ftrace Steven Rostedt
2009-02-17 18:20 ` [PATCH 1/6] ftrace: clean up coding style Steven Rostedt
2009-02-17 18:20 ` [PATCH 2/6] ftrace: rename _hook to _probe Steven Rostedt
2009-02-17 18:20 ` [PATCH 3/6] tracing: use the more proper parameter Steven Rostedt
2009-02-17 18:20 ` [PATCH 4/6] tracing: fix the return value of trace selftest Steven Rostedt
2009-02-17 18:20 ` [PATCH 5/6] tracing: fix typing mistake in hint message and comments Steven Rostedt
2009-02-17 18:20 ` [PATCH 6/6] ftrace: show unlimited when traceon or traceoff has no counter Steven Rostedt
2009-02-18 1:29 ` Steven Rostedt
2009-02-18 0:09 ` [PATCH 0/6] [git pull] updates for tip/tracing/ftrace Ingo Molnar
2009-02-18 8:40 ` Ingo Molnar
2009-02-18 8:57 ` Ingo Molnar
2009-02-18 9:30 ` Ingo Molnar
2009-02-18 17:06 ` Steven Rostedt
2009-02-18 18:19 ` Ingo Molnar [this message]
2009-02-18 14:20 ` Frederic Weisbecker
2009-02-18 16:35 ` Frederic Weisbecker
2009-02-19 8:17 ` Ingo Molnar
2009-02-19 9:16 ` Ingo Molnar
2009-02-19 11:15 ` Ingo Molnar
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=20090218181926.GA26802@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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.