From: Tejun Heo <tj@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Clark Williams <clark@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: workqueue code needing preemption disabled
Date: Mon, 18 Mar 2013 09:43:51 -0700 [thread overview]
Message-ID: <20130318164351.GA21516@mtj.dyndns.org> (raw)
In-Reply-To: <1363624243.25967.178.camel@gandalf.local.home>
Hello, Steven.
On Mon, Mar 18, 2013 at 12:30:43PM -0400, Steven Rostedt wrote:
> If you happen to know the critical areas that require preemption to be
> disabled for real, we can encapsulate them with:
>
> preempt_disable_rt();
>
> preempt_enable_rt();
>
> These are currently only in the -rt patch, but it annotates locations
> that require preemption to be disabled even when -rt converts spin_locks
> into mutexes. These obviously can not contain spin_locks() as
> spin_locks() can block and schedule out.
Making gcwq locks disable preemption would be much safer / easier, but
if that's not desirable, anything touching gcwq->idle_list would be a
good place to start - worker_enter_idle() and worker_leave_idle().
Hmmm... ignoring CPU hotplug, I think those two might just do it.
Give it a try? How reproducible is the problem?
Thanks.
--
tejun
next prev parent reply other threads:[~2013-03-18 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 14:36 Steven Rostedt
2013-03-18 16:06 ` Tejun Heo
2013-03-18 16:23 ` Steven Rostedt
2013-03-18 16:27 ` Steven Rostedt
2013-03-18 16:30 ` Steven Rostedt
2013-03-18 16:43 ` Tejun Heo [this message]
2013-03-18 17:08 ` Steven Rostedt
2013-03-18 18:21 ` Tejun Heo
2013-03-18 18:57 ` Steven Rostedt
2013-03-18 19:06 ` Tejun Heo
2013-03-18 19:19 ` Steven Rostedt
2013-03-18 18:23 ` Steven Rostedt
2013-03-18 18:26 ` Tejun Heo
2013-03-18 18:35 ` Steven Rostedt
2013-03-18 16:27 ` Tejun Heo
2013-03-18 16:41 ` Steven Rostedt
2013-03-18 16:46 ` Tejun Heo
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=20130318164351.GA21516@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=clark@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®