From: Keith Owens <kaos@ocs.com.au>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
rjw@sisk.pl, linux-kernel@vger.kernel.org,
davej@codemonkey.org.uk, mingo@elte.hu, linux@brodo.de,
venkatesh.pallipadi@intel.com
Subject: Re: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64
Date: Sun, 06 Nov 2005 15:32:55 +1100 [thread overview]
Message-ID: <26361.1131251575@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 05 Nov 2005 15:54:07 -0800." <20051105155407.A31099@unix-os.sc.intel.com>
On Sat, 5 Nov 2005 15:54:07 -0800,
Ashok Raj <ashok.raj@intel.com> wrote:
>Since when we already in the cpu notifier callbacks, cpucontrol is already
>held by the cpu_up() or the cpu_down() that caused the double lock.
Add the owning cpu id to the lock. spin_trylock() first, if the lock
is already held then check if the current cpu owns the lock. If it
does then continue, noting (in a local variable) that you do not need
to drop the lock on exit from this recursion level.
next prev parent reply other threads:[~2005-11-06 4:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 15:06 Rafael J. Wysocki
2005-10-31 19:34 ` Andrew Morton
2005-10-31 19:45 ` Rafael J. Wysocki
2005-10-31 20:42 ` Ashok Raj
2005-11-01 19:07 ` Rafael J. Wysocki
2005-11-01 19:14 ` Ashok Raj
2005-11-01 19:44 ` Rafael J. Wysocki
2005-11-01 20:00 ` Ashok Raj
2005-11-01 19:49 ` Lee Revell
2005-11-04 22:30 ` Andrew Morton
2005-11-05 0:00 ` Ashok Raj
2005-11-05 23:19 ` Ashok Raj
2005-11-05 23:33 ` Andrew Morton
2005-11-05 23:54 ` Ashok Raj
2005-11-06 0:06 ` Andrew Morton
2005-11-06 4:32 ` Keith Owens [this message]
2005-10-31 21:42 ` [patch] preempt-trace.patch Ingo Molnar
2005-11-01 19:08 ` Rafael J. Wysocki
2005-11-02 6:27 ` 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64 Dave Jones
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=26361.1131251575@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=venkatesh.pallipadi@intel.com \
/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
Powered by JetHome