From: Andi Kleen <ak@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] scalable timers implementation, 2.4.16, 2.5.0
Date: 06 Dec 2001 03:32:38 +0100 [thread overview]
Message-ID: <p73wv016ptl.fsf@amdsim2.suse.de> (raw)
In-Reply-To: <3C0E9BFD.BC189E17@zip.com.au.suse.lists.linux.kernel> <E16Bo4c-00031f-00@wagner.suse.lists.linux.kernel>
In-Reply-To: Rusty Russell's message of "6 Dec 2001 03:20:47 +0100"
Rusty Russell <rusty@rustcorp.com.au> writes:
> The deadlock you're referring to is, I assume, del_timer_sync() called
> inside the timer itself? Can you think of any other dangerous cases?
Common seems to be:
CPU#0 CPU#1
timer fires
spinlock()
spinlock() - spinning
del_timer_sync()
-> deadlock.
-Andi
next parent reply other threads:[~2001-12-06 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C0E9BFD.BC189E17@zip.com.au.suse.lists.linux.kernel>
[not found] ` <E16Bo4c-00031f-00@wagner.suse.lists.linux.kernel>
2001-12-06 2:32 ` Andi Kleen [this message]
2001-11-27 14:57 [patch] scalable timers implementation, 2.4.16, 2.5.0 Ingo Molnar
2001-12-05 21:29 ` Rusty Russell
2001-12-05 22:13 ` Andrew Morton
2001-12-06 2:15 ` Rusty Russell
2001-12-06 4:20 ` Andrew Morton
2001-12-06 9:10 ` Alan Cox
2001-12-06 10:41 ` 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=p73wv016ptl.fsf@amdsim2.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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