linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, Ingo Molnar <mingo@elte.hu>,
	Steven Rostedt <srostedt@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix TRACING_SUPPORT dependency
Date: Tue, 24 Mar 2009 16:43:50 +1100	[thread overview]
Message-ID: <1237873430.25062.715.camel@pasglop> (raw)
In-Reply-To: <20090320202247.GA30654@oksana.dev.rtsoft.ru>


> > Weird, there's no lockdep support?
> 
> *ashamed*: apparently no such support currently exist for PPC32. ;-)

Actually there is a patch that's been floating around (from Dale
Farnsworth) for adding irqtrace/lockdep to ppc32 but it seems to be
buggy :-) IE, it causes crashes and I haven't had a chance
to try to find out yet. I'll probably give it another go one of these
days, but if you want to play with it, I'll send it to you directly.

Cheers,
Ben.

  parent reply	other threads:[~2009-03-24  5:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 15:09 [PATCH] tracing: Fix TRACING_SUPPORT dependency Anton Vorontsov
2009-03-20 19:04 ` Ingo Molnar
2009-03-20 19:39   ` Anton Vorontsov
2009-03-20 19:57     ` Ingo Molnar
2009-03-20 20:22       ` Anton Vorontsov
2009-03-21 16:18         ` Ingo Molnar
2009-03-21 16:31           ` Steven Rostedt
2009-03-21 16:33             ` Ingo Molnar
2009-03-21 16:41               ` Steven Rostedt
2009-03-21 16:43                 ` Steven Rostedt
2009-03-21 16:46                   ` Ingo Molnar
2009-03-23 22:07           ` [PATCH] tracing: Fix TRACING_SUPPORT dependency for PPC32 Anton Vorontsov
2009-03-24  0:51             ` Steven Rostedt
2009-03-24  5:43         ` Benjamin Herrenschmidt [this message]
2009-03-21  3:09       ` [PATCH] tracing: Fix TRACING_SUPPORT dependency 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=1237873430.25062.715.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@elte.hu \
    --cc=srostedt@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).