From: Thomas Hellstrom <thellstrom@vmware.com>
To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
peterz@infradead.org
Cc: linux-graphics-maintainer@vmware.com, pv-drivers@vmware.com,
Thomas Hellstrom <thellstrom@vmware.com>
Subject: [PATCH v4 3/3] drm: Change deadlock-avoidance algorithm for the modeset locks.
Date: Tue, 19 Jun 2018 10:24:45 +0200 [thread overview]
Message-ID: <20180619082445.11062-4-thellstrom@vmware.com> (raw)
In-Reply-To: <20180619082445.11062-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.
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
---
v2, v3, v4: Adjusted to API changes.
---
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 638be2eb67b4..8a5100685875 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_WD_CLASS(crtc_ww_class);
+static DEFINE_WW_CLASS(crtc_ww_class);
/**
* drm_modeset_lock_all - take all modeset locks
--
2.14.3
next prev parent reply other threads:[~2018-06-19 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 8:24 [PATCH v4 0/4] locking,drm: Fix ww mutex naming / algorithm inconsistency Thomas Hellstrom
2018-06-19 8:24 ` [PATCH 1/3] locking: WW mutex cleanup Thomas Hellstrom
2018-06-19 9:44 ` Peter Zijlstra
2018-06-19 10:44 ` Thomas Hellstrom
2018-06-19 11:02 ` Peter Zijlstra
2018-06-19 8:24 ` [PATCH v4 2/3] locking: Implement an algorithm choice for Wound-Wait mutexes Thomas Hellstrom
2018-06-19 9:45 ` Peter Zijlstra
2019-01-16 14:24 ` Rob Clark
2019-01-16 16:48 ` Thomas Hellstrom
2019-01-17 12:47 ` Rob Clark
2018-06-19 8:24 ` Thomas Hellstrom [this message]
2018-06-19 9:45 ` [PATCH v4 0/4] locking,drm: Fix ww mutex naming / algorithm inconsistency Peter Zijlstra
2018-06-20 5:17 ` Thomas Hellstrom
2018-06-21 10:56 ` Ingo Molnar
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=20180619082445.11062-4-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pv-drivers@vmware.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