From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
Badari Pulavarty <pbadari@us.ibm.com>,
dhowells@redhat.com, torvalds@osdl.org, suparna@in.ibm.com,
linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rwsem: Make rwsems use interrupt disabling spinlocks
Date: Fri, 11 Mar 2005 10:40:24 +0100 [thread overview]
Message-ID: <20050311094024.GC19954@elte.hu> (raw)
In-Reply-To: <1110399036.6280.151.camel@laptopd505.fenrus.org>
* Arjan van de Ven <arjan@infradead.org> wrote:
> > Ingo, we already have a touch_nmi_watchdog() in the sysrq code. It might be
> > worth adding a touch_softlockup_watchdog() wherever we have a
> > touch_nmi_watchdog().
>
> ....or add touch_softlockup_watchdog to touch_nmi_watchdog() instead
> and rename it tickle_watchdog() overtime.
you mean like:
+extern void touch_softlockup_watchdog(void);
in:
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm2/broken-out/detect-soft-lockups.patch
?
Ingo
next prev parent reply other threads:[~2005-03-11 9:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050308170107.231a145c.akpm@osdl.org>
[not found] ` <1110327267.24286.139.camel@dyn318077bld.beaverton.ibm.com>
[not found] ` <18744.1110364438@redhat.com>
2005-03-09 11:04 ` aio stress panic on 2.6.11-mm1 Suparna Bhattacharya
2005-03-09 11:05 ` Andrew Morton
2005-03-09 11:07 ` Arjan van de Ven
2005-03-09 11:17 ` Andi Kleen
2005-03-09 11:28 ` Andrew Morton
2005-03-09 11:59 ` David Howells
2005-03-09 12:12 ` [PATCH] rwsem: Make rwsems use interrupt disabling spinlocks David Howells
2005-03-09 17:35 ` Badari Pulavarty
2005-03-09 19:18 ` Badari Pulavarty
2005-03-09 19:16 ` Badari Pulavarty
2005-03-09 19:42 ` Andrew Morton
2005-03-09 20:10 ` Arjan van de Ven
2005-03-11 9:40 ` Ingo Molnar [this message]
2005-03-11 10:07 ` Andrew Morton
2005-03-11 10:25 ` Ingo Molnar
2005-03-09 11:10 ` aio stress panic on 2.6.11-mm1 Arjan van de Ven
2005-03-09 11:21 ` Andi Kleen
2005-03-09 14:48 ` Suparna Bhattacharya
2005-03-09 21:58 ` David Howells
2005-03-09 11:11 ` Andi Kleen
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=20050311094024.GC19954@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=suparna@in.ibm.com \
--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.