From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, discuss@x86-64.org, torvalds@osdl.org,
cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] [7/7] x86_64: Move ondemand timer into own work queue
Date: Fri, 5 May 2006 15:09:45 -0400 [thread overview]
Message-ID: <20060505190945.GG9937@redhat.com> (raw)
In-Reply-To: <445B9A6A.mailIZ41BYSAC@suse.de>
On Fri, May 05, 2006 at 08:33:14PM +0200, Andi Kleen wrote:
>
> Taking the cpu hotplug semaphore in a normal events workqueue
> is unsafe because other tasks can wait for any workqueues with
> it hold. This results in a deadlock.
>
> Move the DBS timer into its own work queue which is not
> affected by other work queue flushes to avoid this.
>
> Cc: venkatesh.pallipadi@intel.com
> Cc: cpufreq@lists.linux.org.uk
>
> Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Dave Jones <davej@redhat.com>
(I'm up to my eyes in various real-world crisis right now, so git maintainence
is slacking for a month)
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-05-05 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 18:33 [PATCH] [7/7] x86_64: Move ondemand timer into own work queue Andi Kleen
2006-05-05 19:09 ` Dave Jones [this message]
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=20060505190945.GG9937@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=discuss@x86-64.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox