From: Andi Kleen <ak@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
Badari Pulavarty <pbadari@us.ibm.com>, Jan Kara <jack@suse.cz>,
torvalds@osdl.org, stable@kernel.org,
ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [patch 003/152] jbd: fix commit of ordered data buffers
Date: Fri, 29 Sep 2006 21:54:30 +0200 [thread overview]
Message-ID: <200609292154.30234.ak@suse.de> (raw)
In-Reply-To: <20060929191759.GA19304@elte.hu>
On Friday 29 September 2006 21:18, Ingo Molnar wrote:
>
> * Andrew Morton <akpm@osdl.org> wrote:
>
> > gad, there have been so many all-CPU-backtrace patches over the years.
> >
> > <optimistically cc's Ingo>
> >
> > Ingo, do you think that's something which we shuld have in the
> > spinlock debugging code? A trace to let us see which CPU is holding
> > that lock, and where from? I guess if the other cpu is stuck in
> > spin_lock_irqsave() then we'll get stuck delivering the IPI, so it'd
> > need to be async.
>
> used to have this in -rt for i686 and x86_64 for the NMI watchdog tick
> to print on all CPUs, in the next tick (i.e. no need to actually
> initiate an IPI) - but it was all a bit hacky [but worked]. It fell
> victim to some recent flux in that area.
You mean spinlock debugging setting a global variable and the NMI
watchdog testing that? Makes sense. I can put it on my todo list.
-Andi
next prev parent reply other threads:[~2006-09-29 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609260630.k8Q6UrvQ011999@shell0.pdx.osdl.net>
[not found] ` <451C4DDE.60307@us.ibm.com>
[not found] ` <20060929090253.GA17124@atrey.karlin.mff.cuni.cz>
2006-09-29 16:11 ` [patch 003/152] jbd: fix commit of ordered data buffers Badari Pulavarty
2006-09-29 19:20 ` Andrew Morton
2006-09-29 19:18 ` Ingo Molnar
2006-09-29 19:54 ` Andi Kleen [this message]
2006-09-29 20:20 ` Andrew Morton
2006-09-29 21:22 ` Ingo Molnar
2006-09-29 21:26 ` 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=200609292154.30234.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pbadari@us.ibm.com \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
/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.