From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Prevent spinlock debug from timing out too early
Date: Mon, 6 Feb 2006 22:36:18 +0100 [thread overview]
Message-ID: <20060206213618.GA28566@elte.hu> (raw)
In-Reply-To: <200602062216.28943.ak@suse.de>
* Andi Kleen <ak@suse.de> wrote:
> Index: linux-2.6.15/lib/spinlock_debug.c
> ===================================================================
> --- linux-2.6.15.orig/lib/spinlock_debug.c
> +++ linux-2.6.15/lib/spinlock_debug.c
> @@ -68,13 +68,13 @@ static inline void debug_spin_unlock(spi
> static void __spin_lock_debug(spinlock_t *lock)
> {
> int print_once = 1;
> - u64 i;
>
> for (;;) {
> - for (i = 0; i < loops_per_jiffy * HZ; i++) {
> - cpu_relax();
> + unsigned long timeout = jiffies + HZ;
> + while (time_before(jiffies, timeout)) {
> if (__raw_spin_trylock(&lock->raw_lock))
> return;
> + cpu_relax();
The reason i added a loop counter was to solve the case where we are
spinning with interrupts disabled - jiffies wont increase there! But i
agree that loops_per_jiffy is the wrong metric to use.
a better solution would be to call __delay(1) after the first failed
attempt, that would make the delay at least 1 second long. It seems
__delay() is de-facto exported by every architecture, so we can rely on
it in the global spinlock code.
So how about the patch below instead?
[detail: i moved the __delay() after the second attempted trylock, this
way we'll have 2 trylocks without a delay - for ultra-short critical
sections.]
Ingo
----
fix spinlock debugging delays to not time out too early.
Bug found by Andi Kleen.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
--- linux/lib/spinlock_debug.c.orig
+++ linux/lib/spinlock_debug.c
@@ -72,9 +72,9 @@ static void __spin_lock_debug(spinlock_t
for (;;) {
for (i = 0; i < loops_per_jiffy * HZ; i++) {
- cpu_relax();
if (__raw_spin_trylock(&lock->raw_lock))
return;
+ __delay(1);
}
/* lockup suspected: */
if (print_once) {
@@ -144,9 +144,9 @@ static void __read_lock_debug(rwlock_t *
for (;;) {
for (i = 0; i < loops_per_jiffy * HZ; i++) {
- cpu_relax();
if (__raw_read_trylock(&lock->raw_lock))
return;
+ __delay(1);
}
/* lockup suspected: */
if (print_once) {
@@ -217,9 +217,9 @@ static void __write_lock_debug(rwlock_t
for (;;) {
for (i = 0; i < loops_per_jiffy * HZ; i++) {
- cpu_relax();
if (__raw_write_trylock(&lock->raw_lock))
return;
+ __delay(1);
}
/* lockup suspected: */
if (print_once) {
next prev parent reply other threads:[~2006-02-06 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 21:16 [PATCH] Prevent spinlock debug from timing out too early Andi Kleen
2006-02-06 21:36 ` Ingo Molnar [this message]
2006-02-06 21:42 ` Andi Kleen
2006-02-06 23:22 ` 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=20060206213618.GA28566@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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.