From: Johannes Berg <johannes@sipsolutions.net>
To: Tim Pepper <lnxninja@us.ibm.com>
Cc: External List <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC/PATCH 0/2] powerpc: 64 bits irqtrace / lockdep support
Date: Wed, 07 Nov 2007 11:22:20 +0100 [thread overview]
Message-ID: <1194430940.4055.14.camel@johannes.berg> (raw)
In-Reply-To: <eada2a070711061136l18ac7651h85bf3da19a79b669@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Tue, 2007-11-06 at 11:36 -0800, Tim Pepper wrote:
> On 10/14/07, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > This is 2 patches, one from Christoph Hellwig that adds the backtrace support,
> > and one from Johannes Berg modified by me that adds the irq tracing support.
> >
> > This successfully boots a POWER5 pSeries machine. I'm going to run some more
> > tests in the upcoming few days, so this is not an official submission (and it's
> > too late for .24 merge window anyway) but it's looking good so far.
>
> FYI: Boots and survives watching /proc/lock_stat during a kernel build
> for me (on a 970 based blade).
Hmm. I should give it another try and see why it breaks for me. Could be
CONFIG_HIBERNATION related maybe.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2007-11-07 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 7:28 [RFC/PATCH 0/2] powerpc: 64 bits irqtrace / lockdep support Benjamin Herrenschmidt
2007-10-15 7:28 ` [RFC/PATCH 1/2] powerpc: lockdep stacktrace support Benjamin Herrenschmidt
2007-10-15 7:28 ` [RFC/PATCH 2/2] powerpc: irqtrace support to 64-bit powerpc Benjamin Herrenschmidt
2007-10-15 8:41 ` Johannes Berg
2007-10-15 9:25 ` Benjamin Herrenschmidt
2007-10-22 13:35 ` Johannes Berg
2007-10-22 20:14 ` Benjamin Herrenschmidt
2007-11-06 19:36 ` [RFC/PATCH 0/2] powerpc: 64 bits irqtrace / lockdep support Tim Pepper
2007-11-07 10:22 ` Johannes Berg [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=1194430940.4055.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=lnxninja@us.ibm.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).