From: Andrew Morton <akpm@osdl.org>
To: ego@in.ibm.com, Oleg Nesterov <oleg@tv-sign.ru>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
linux-kernel@vger.kernel.org, David Wilder <dwilder@us.ibm.com>,
Tom Zanussi <zanussi@us.ibm.com>, Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Christoph Hellwig <hch@infradead.org>,
ltt-dev@shafik.org, systemtap@sources.redhat.com,
Douglas Niehaus <niehaus@eecs.ku.edu>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Thomas Gleixner <tglx@linutronix.de>,
kiran@scalex86.org, venkatesh.pallipadi@intel.com,
dipankar@in.ibm.com, vatsa@in.ibm.com, torvalds@osdl.org,
davej@redhat.com
Subject: Re: [PATCH] Relay CPU Hotplug support
Date: Fri, 22 Dec 2006 02:44:58 -0800 [thread overview]
Message-ID: <20061222024458.322adffd.akpm@osdl.org> (raw)
In-Reply-To: <20061222103724.GA29348@in.ibm.com>
On Fri, 22 Dec 2006 16:07:24 +0530
Gautham R Shenoy <ego@in.ibm.com> wrote:
> While we are at this per-subsystem cpuhotplug "locking", here's a
> proposal that might put an end to the workqueue deadlock woes.
Oleg is working on some patches which will permit us to cancel or wait upon
a particular work_struct, rather than upon all pending work_structs.
This will fix the problem where we accidentlly wait upon some unrelated
work_struct which takes a lock which is related to one which we already
hold.
I hope. It'll be a bit tricky to implement: if some foreign work_struct is
running right now, we cannot wait upon it - we must non-blockingly dequeue
the work_struct which we want to kill before it gets to run.
next prev parent reply other threads:[~2006-12-22 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 0:31 Mathieu Desnoyers
2006-12-21 1:13 ` Tom Zanussi
2006-12-21 3:22 ` Mathieu Desnoyers
2006-12-21 7:23 ` Andrew Morton
2006-12-21 7:04 ` Tom Zanussi
2006-12-22 10:37 ` Gautham R Shenoy
2006-12-22 10:44 ` Andrew Morton [this message]
2006-12-22 16:20 ` Oleg Nesterov
2006-12-22 16:42 ` Oleg Nesterov
2006-12-22 20:01 ` Gautham R Shenoy
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=20061222024458.322adffd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dwilder@us.ibm.com \
--cc=ego@in.ibm.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=mingo@redhat.com \
--cc=niehaus@eecs.ku.edu \
--cc=oleg@tv-sign.ru \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.org \
--cc=vatsa@in.ibm.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=zanussi@us.ibm.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
all inboxes | Powered by JetHome®