From: Peter Zijlstra <peterz@infradead.org>
To: "Nicolai Hähnle" <nhaehnle@gmail.com>
Cc: "Maarten Lankhorst" <dev@mblankhorst.nl>,
"Nicolai Hähnle" <Nicolai.Haehnle@amd.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Ingo Molnar" <mingo@redhat.com>
Subject: Re: [PATCH v2 01/11] drm/vgem: Use ww_mutex_(un)lock even with a NULL context
Date: Thu, 1 Dec 2016 17:24:35 +0100 [thread overview]
Message-ID: <20161201162435.GK3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1480601214-26583-2-git-send-email-nhaehnle@gmail.com>
Just to let you know, I've not been ignoring all the ww_mutex stuff,
I've been ill this week. I'm slowly returning to feeling human again,
but am still fairly wrecked.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: "Nicolai Hähnle" <nhaehnle@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Nicolai Hähnle" <Nicolai.Haehnle@amd.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Maarten Lankhorst" <dev@mblankhorst.nl>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 01/11] drm/vgem: Use ww_mutex_(un)lock even with a NULL context
Date: Thu, 1 Dec 2016 17:24:35 +0100 [thread overview]
Message-ID: <20161201162435.GK3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1480601214-26583-2-git-send-email-nhaehnle@gmail.com>
Just to let you know, I've not been ignoring all the ww_mutex stuff,
I've been ill this week. I'm slowly returning to feeling human again,
but am still fairly wrecked.
next prev parent reply other threads:[~2016-12-01 16:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 14:06 [PATCH v2 00/11] locking/ww_mutex: Keep sorted wait list to avoid stampedes Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 01/11] drm/vgem: Use ww_mutex_(un)lock even with a NULL context Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:18 ` Chris Wilson
2016-12-01 14:18 ` Chris Wilson
2016-12-01 15:14 ` Daniel Vetter
2016-12-01 16:24 ` Peter Zijlstra [this message]
2016-12-01 16:24 ` Peter Zijlstra
2016-12-01 14:06 ` [PATCH v2 02/11] locking/ww_mutex: Re-check ww->ctx in the inner optimistic spin loop Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:36 ` Chris Wilson
2016-12-01 14:36 ` Chris Wilson
2016-12-06 15:06 ` Peter Zijlstra
2016-12-06 15:06 ` Peter Zijlstra
2016-12-06 16:03 ` Waiman Long
2016-12-06 18:29 ` Peter Zijlstra
2016-12-06 18:29 ` Peter Zijlstra
2016-12-06 18:46 ` Waiman Long
2016-12-01 14:06 ` [PATCH v2 03/11] locking/ww_mutex: Extract stamp comparison to __ww_mutex_stamp_after Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:42 ` Chris Wilson
2016-12-01 14:42 ` Chris Wilson
2016-12-01 14:06 ` [PATCH v2 04/11] locking/ww_mutex: Set use_ww_ctx even when locking without a context Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-06 15:14 ` Peter Zijlstra
2016-12-06 15:14 ` Peter Zijlstra
2016-12-06 15:25 ` Peter Zijlstra
2016-12-06 15:25 ` Peter Zijlstra
2016-12-16 13:17 ` Nicolai Hähnle
2016-12-16 13:17 ` Nicolai Hähnle
2016-12-17 7:53 ` Maarten Lankhorst
2016-12-17 7:53 ` Maarten Lankhorst
2016-12-17 13:49 ` Peter Zijlstra
2016-12-17 13:49 ` Peter Zijlstra
2016-12-01 14:06 ` [PATCH v2 05/11] locking/ww_mutex: Add waiters in stamp order Nicolai Hähnle
2016-12-01 15:59 ` Chris Wilson
2016-12-01 15:59 ` Chris Wilson
2016-12-16 14:21 ` Nicolai Hähnle
2016-12-16 14:21 ` Nicolai Hähnle
2016-12-06 15:36 ` Peter Zijlstra
2016-12-06 15:36 ` Peter Zijlstra
2016-12-16 13:34 ` Nicolai Hähnle
2016-12-16 13:34 ` Nicolai Hähnle
2016-12-06 16:55 ` Peter Zijlstra
2016-12-06 16:55 ` Peter Zijlstra
2016-12-16 14:19 ` Nicolai Hähnle
2016-12-16 14:19 ` Nicolai Hähnle
2016-12-16 14:46 ` Peter Zijlstra
2016-12-16 14:46 ` Peter Zijlstra
2016-12-16 17:15 ` Peter Zijlstra
2016-12-16 17:15 ` Peter Zijlstra
2016-12-16 18:11 ` Nicolai Hähnle
2016-12-16 20:00 ` Peter Zijlstra
2016-12-16 20:00 ` Peter Zijlstra
2016-12-16 22:35 ` Nicolai Hähnle
2016-12-16 17:20 ` Peter Zijlstra
2016-12-16 17:20 ` Peter Zijlstra
2016-12-16 18:12 ` Nicolai Hähnle
2016-12-16 18:12 ` Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 06/11] locking/ww_mutex: Notify waiters that have to back off while adding tasks to wait list Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 07/11] locking/ww_mutex: Wake at most one waiter for back off when acquiring the lock Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 08/11] locking/ww_mutex: Yield to other waiters from optimistic spin Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 09/11] locking/mutex: Initialize mutex_waiter::ww_ctx with poison when debugging Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 10/11] Documentation/locking/ww_mutex: Update the design document Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
2016-12-01 14:06 ` [PATCH v2 11/11] [rfc] locking/ww_mutex: Always spin optimistically for the first waiter Nicolai Hähnle
2016-12-01 14:06 ` Nicolai Hähnle
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=20161201162435.GK3092@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Nicolai.Haehnle@amd.com \
--cc=dev@mblankhorst.nl \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nhaehnle@gmail.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 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.