From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: [patch] locking/lglocks: use preempt_enable/disable_nort() in lg_double_lock/lg_double_unlock
Date: Sat, 27 Feb 2016 08:34:43 +0100 [thread overview]
Message-ID: <1456558483.3759.18.camel@gmail.com> (raw)
In-Reply-To: <1456556755.3759.4.camel@gmail.com>
Let's not do that when snagging an rtmutex.
Signed-off-by: Mike Galbraith <umgwanakilbuti@gmail.com>
---
kernel/locking/lglock.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/kernel/locking/lglock.c
+++ b/kernel/locking/lglock.c
@@ -86,7 +86,7 @@ void lg_double_lock(struct lglock *lg, i
if (cpu2 < cpu1)
swap(cpu1, cpu2);
- preempt_disable();
+ preempt_disable_nort();
lock_acquire_shared(&lg->lock_dep_map, 0, 0, NULL, _RET_IP_);
lg_do_lock(per_cpu_ptr(lg->lock, cpu1));
lg_do_lock(per_cpu_ptr(lg->lock, cpu2));
@@ -97,7 +97,7 @@ void lg_double_unlock(struct lglock *lg,
lock_release(&lg->lock_dep_map, 1, _RET_IP_);
lg_do_unlock(per_cpu_ptr(lg->lock, cpu1));
lg_do_unlock(per_cpu_ptr(lg->lock, cpu2));
- preempt_enable();
+ preempt_enable_nort();
}
void lg_global_lock(struct lglock *lg)
next prev parent reply other threads:[~2016-02-27 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 7:05 [patch] rt,workqueue: Fix blocking call when !TASK_RUNNING splat in rescuer_thread() Mike Galbraith
2016-02-27 7:09 ` [patch] drm,radeon,i915: use preempt_disable/enable_rt() where recommended Mike Galbraith
2016-02-27 7:34 ` Mike Galbraith [this message]
2016-02-27 8:01 ` [patch] drm,i915: Use local_lock/unlock_irq() in intel_pipe_update_start/end() Mike Galbraith
2016-02-27 9:04 ` [patch] rt,workqueue: Fix blocking call when !TASK_RUNNING splat in rescuer_thread() Thomas Gleixner
2016-02-27 9:14 ` Thomas Gleixner
2016-02-27 9:16 ` Thomas Gleixner
2016-02-27 12:11 ` Mike Galbraith
2016-02-27 13:48 ` Mike Galbraith
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=1456558483.3759.18.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.