From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
john stultz <johnstul@us.ibm.com>,
Roman Zippel <zippel@linux-m68k.org>,
Christian Borntraeger <cborntra@de.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] timer/hrtimer: take per cpu locks in sane order
Date: Fri, 2 Mar 2007 14:04:33 +0100 [thread overview]
Message-ID: <20070302130433.GA4391@elte.hu> (raw)
In-Reply-To: <20070302125848.GA8226@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> - spin_lock(&new_base->lock);
> - spin_lock(&old_base->lock);
> + /*
> + * If we take a lock from a different cpu, make sure we have always
> + * the same locking order. That is the lock that belongs to the cpu
> + * with the lowest number is taken first.
> + */
> + lock1 = smp_processor_id() < cpu ? &new_base->lock : &old_base->lock;
> + lock2 = smp_processor_id() < cpu ? &old_base->lock : &new_base->lock;
> + spin_lock(lock1);
> + spin_lock(lock2);
looks good to me. Wouldnt this be cleaner via double_lock_timer() -
similar to how double_rq_lock() works in kernel/sched.c - instead of
open-coding it?
Ingo
next prev parent reply other threads:[~2007-03-02 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 15:30 timer/hrtimer & cpu hotplug lockdep complaints Heiko Carstens
2007-03-02 12:58 ` [patch] timer/hrtimer: take per cpu locks in sane order Heiko Carstens
2007-03-02 13:04 ` Ingo Molnar [this message]
2007-03-02 14:23 ` Heiko Carstens
2007-03-02 16:48 ` Andrew Morton
2007-03-02 19:08 ` Heiko Carstens
2007-03-02 19:45 ` Andrew Morton
2007-03-02 21:39 ` Heiko Carstens
2007-03-02 22:47 ` Heiko Carstens
2007-03-04 23:24 ` Matt Mackall
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=20070302130433.GA4391@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=cborntra@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox