From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Corbet <corbet@lwn.net>,
pv-drivers@vmware.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Josh Triplett <josh@joshtriplett.org>,
linaro-mm-sig@lists.linaro.org, David Airlie <airlied@linux.ie>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>,
linux-graphics-maintainer@vmware.com,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 1/3] locking: WW mutex cleanup
Date: Tue, 19 Jun 2018 13:02:05 +0200 [thread overview]
Message-ID: <20180619110205.GE2476@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <8ea67e74-5ed4-2157-8e51-43f15047b3e4@vmware.com>
On Tue, Jun 19, 2018 at 12:44:52PM +0200, Thomas Hellstrom wrote:
> On 06/19/2018 11:44 AM, Peter Zijlstra wrote:
> > On Tue, Jun 19, 2018 at 10:24:43AM +0200, Thomas Hellstrom wrote:
> > > From: Peter Ziljstra <peterz@infradead.org>
> > >
> > > Make the WW mutex code more readable by adding comments, splitting up
> > > functions and pointing out that we're actually using the Wait-Die
> > > algorithm.
> > >
> > > Cc: Ingo Molnar <mingo@redhat.com>
> > > Cc: Jonathan Corbet <corbet@lwn.net>
> > > Cc: Gustavo Padovan <gustavo@padovan.org>
> > > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > > Cc: Sean Paul <seanpaul@chromium.org>
> > > Cc: David Airlie <airlied@linux.ie>
> > > Cc: Davidlohr Bueso <dave@stgolabs.net>
> > > Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > Cc: Josh Triplett <josh@joshtriplett.org>
> > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > Cc: Kate Stewart <kstewart@linuxfoundation.org>
> > > Cc: Philippe Ombredanne <pombredanne@nexb.com>
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: linux-doc@vger.kernel.org
> > > Cc: linux-media@vger.kernel.org
> > > Cc: linaro-mm-sig@lists.linaro.org
> > > Co-authored-by: Thomas Hellstrom <thellstrom@vmware.com>
> > > Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
> > > ---
> > > Documentation/locking/ww-mutex-design.txt | 12 +-
> > > include/linux/ww_mutex.h | 28 ++---
> > > kernel/locking/mutex.c | 202 ++++++++++++++++++------------
> > > 3 files changed, 145 insertions(+), 97 deletions(-)
> > Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> Hi Peter,
>
> Do you want to add a SOB, since you're the main author?
Sure, here goes:
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-19 11:02 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 [this message]
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 ` [PATCH v4 3/3] drm: Change deadlock-avoidance algorithm for the modeset locks Thomas Hellstrom
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=20180619110205.GE2476@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=josh@joshtriplett.org \
--cc=kstewart@linuxfoundation.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pombredanne@nexb.com \
--cc=pv-drivers@vmware.com \
--cc=tglx@linutronix.de \
--cc=thellstrom@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