From: Thomas Hellstrom <thellstrom@vmware.com>
To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Thomas Hellstrom <thellstrom@vmware.com>
Subject: [PATCH 2/2] drm: Change deadlock-avoidance algorithm for the modeset locks.
Date: Wed, 13 Jun 2018 09:47:45 +0200 [thread overview]
Message-ID: <20180613074745.14750-3-thellstrom@vmware.com> (raw)
In-Reply-To: <20180613074745.14750-1-thellstrom@vmware.com>
For modeset locks we don't expect a high number of contending
transactions so change algorithm from Wait-Die to Wound-Wait.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
---
drivers/gpu/drm/drm_modeset_lock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_modeset_lock.c b/drivers/gpu/drm/drm_modeset_lock.c
index f22a7ef41de1..294997765a2c 100644
--- a/drivers/gpu/drm/drm_modeset_lock.c
+++ b/drivers/gpu/drm/drm_modeset_lock.c
@@ -70,7 +70,7 @@
* lists and lookup data structures.
*/
-static DEFINE_WW_CLASS(crtc_ww_class, true);
+static DEFINE_WW_CLASS(crtc_ww_class, false);
/**
* drm_modeset_lock_all - take all modeset locks
--
2.14.3
prev parent reply other threads:[~2018-06-13 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 7:47 [PATCH 0/2] locking,drm: Fix ww mutex naming / algorithm inconsistency Thomas Hellstrom
2018-06-13 7:47 ` [PATCH 1/2] locking: Implement an algorithm choice for Wound-Wait mutexes Thomas Hellstrom
2018-06-13 7:54 ` Greg Kroah-Hartman
2018-06-13 8:34 ` Thomas Hellstrom
2018-06-13 9:50 ` Peter Zijlstra
2018-06-13 10:40 ` Thomas Hellstrom
2018-06-13 13:10 ` Peter Zijlstra
2018-06-13 14:05 ` Thomas Hellstrom
2018-06-14 10:51 ` Peter Zijlstra
2018-06-14 11:48 ` Thomas Hellstrom
2018-06-14 14:42 ` Peter Zijlstra
2018-06-14 16:43 ` Thomas Hellstrom
2018-06-14 18:51 ` Peter Zijlstra
2018-06-15 12:07 ` Thomas Hellstrom
2018-06-13 7:47 ` Thomas Hellstrom [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=20180613074745.14750-3-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).