From: Lee Revell <rlrevell@joe-job.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Juergen Kreileder <jk@blackdown.de>,
Andrew Morton <akpm@osdl.org>, Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org, maneesh@in.ibm.com
Subject: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
Date: Mon, 02 May 2005 21:24:13 -0400 [thread overview]
Message-ID: <1115083453.27658.6.camel@mindpipe> (raw)
In-Reply-To: <1115079230.6155.35.camel@gaston>
On Tue, 2005-05-03 at 10:13 +1000, Benjamin Herrenschmidt wrote:
> Well, there may be other issues brought by this new timer code though.
> I'm running G5s regulary without a lockup or anything for weeks, so it
> would be interesting if you could try to find out what's involved in
> that other lockup you had.
It seems like it would not be to hard to create a timer test suite that
just hammers the timer subsystem, creating and deleting and modifying
zillions of timers, changing the system time, etc. Combined with
running with HZ=10000 or something it seems like you could shake out
bugs a lot faster than just running & waiting for a race to show up.
I've seen timer related issues (the set_rtc_mmss issue that George
Anzinger fixed) while testing the RT patchset that I could only ever
reproduce once.
Lee
next prev parent reply other threads:[~2005-05-03 1:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 7:55 [PATCH] fix __mod_timer vs __run_timers deadlock Oleg Nesterov
2005-05-01 9:31 ` Andrew Morton
2005-05-02 22:50 ` Juergen Kreileder
2005-05-03 0:13 ` Benjamin Herrenschmidt
2005-05-03 1:24 ` Lee Revell [this message]
2005-05-03 1:28 ` Benjamin Herrenschmidt
2005-05-03 1:33 ` Zwane Mwaikambo
2005-05-03 1:35 ` Juergen Kreileder
2005-05-03 2:48 ` Paul Mackerras
2005-05-03 18:51 ` David S. Miller
2005-05-03 23:44 ` Benjamin Herrenschmidt
2005-05-03 23:39 ` David S. Miller
2005-05-04 0:05 ` Benjamin Herrenschmidt
2005-05-02 4:08 ` Maneesh Soni
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=1115083453.27658.6.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=jk@blackdown.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=oleg@tv-sign.ru \
/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.