From: "Nicolai Hähnle" <nhaehnle@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
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 04/11] locking/ww_mutex: Set use_ww_ctx even when locking without a context
Date: Fri, 16 Dec 2016 14:17:25 +0100 [thread overview]
Message-ID: <239fa361-331a-a7b6-9a0d-a6baa19a5003@gmail.com> (raw)
In-Reply-To: <20161206152537.GV3045@worktop.programming.kicks-ass.net>
On 06.12.2016 16:25, Peter Zijlstra wrote:
> On Thu, Dec 01, 2016 at 03:06:47PM +0100, Nicolai Hähnle wrote:
>
>> @@ -640,10 +640,11 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass,
>> struct mutex_waiter waiter;
>> unsigned long flags;
>> bool first = false;
>> - struct ww_mutex *ww;
>> int ret;
>>
>> - if (use_ww_ctx) {
>> + if (use_ww_ctx && ww_ctx) {
>> + struct ww_mutex *ww;
>> +
>> ww = container_of(lock, struct ww_mutex, base);
>> if (unlikely(ww_ctx == READ_ONCE(ww->ctx)))
>> return -EALREADY;
>
> So I don't see the point of removing *ww from the function scope, we can
> still compute that container_of() even if !ww_ctx, right? That would
> safe a ton of churn below, adding all those struct ww_mutex declarations
> and container_of() casts.
>
> (and note that the container_of() is a fancy NO-OP because base is the
> first member).
Sorry for taking so long to get back to you.
In my experience, the undefined behavior sanitizer in GCC for userspace
programs complains about merely casting a pointer to the wrong type. I
never went into the standards rabbit hole to figure out the details. It
might be a C++ only thing (ubsan cannot tell the difference otherwise
anyway), but that was the reason for doing the change in this more
complicated way.
Are you sure that this is defined behavior in C? If so, I'd be happy to
go with the version that has less churn.
I'll also get rid of those ww_mutex_lock* wrapper functions.
Thanks,
Nicolai
>
>> @@ -656,8 +657,12 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass,
>> mutex_optimistic_spin(lock, ww_ctx, use_ww_ctx, false)) {
>> /* got the lock, yay! */
>> lock_acquired(&lock->dep_map, ip);
>> - if (use_ww_ctx)
>> + if (use_ww_ctx && ww_ctx) {
>> + struct ww_mutex *ww;
>> +
>> + ww = container_of(lock, struct ww_mutex, base);
>> ww_mutex_set_context_fastpath(ww, ww_ctx);
>> + }
>> preempt_enable();
>> return 0;
>> }
>> @@ -702,7 +707,7 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass,
>> goto err;
>> }
>>
>> - if (use_ww_ctx && ww_ctx->acquired > 0) {
>> + if (use_ww_ctx && ww_ctx && ww_ctx->acquired > 0) {
>> ret = __ww_mutex_lock_check_stamp(lock, ww_ctx);
>> if (ret)
>> goto err;
>> @@ -742,8 +747,12 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass,
>> /* got the lock - cleanup and rejoice! */
>> lock_acquired(&lock->dep_map, ip);
>>
>> - if (use_ww_ctx)
>> + if (use_ww_ctx && ww_ctx) {
>> + struct ww_mutex *ww;
>> +
>> + ww = container_of(lock, struct ww_mutex, base);
>> ww_mutex_set_context_slowpath(ww, ww_ctx);
>> + }
>>
>> spin_unlock_mutex(&lock->wait_lock, flags);
>> preempt_enable();
>
> All that then reverts to:
>
> - if (use_ww_ctx)
> + if (use_ww_ctx && ww_ctx)
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-12-16 13:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1480601214-26583-1-git-send-email-nhaehnle@gmail.com>
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:18 ` Chris Wilson
2016-12-01 15:14 ` Daniel Vetter
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:36 ` Chris Wilson
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: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: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-06 15:14 ` Peter Zijlstra
2016-12-06 15:25 ` Peter Zijlstra
2016-12-16 13:17 ` Nicolai Hähnle [this message]
2016-12-17 7:53 ` Maarten Lankhorst
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-16 14:21 ` Nicolai Hähnle
2016-12-06 15:36 ` Peter Zijlstra
2016-12-16 13:34 ` Nicolai Hähnle
2016-12-06 16:55 ` Peter Zijlstra
2016-12-16 14:19 ` Nicolai Hähnle
2016-12-16 14:46 ` 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 22:35 ` Nicolai Hähnle
2016-12-16 17:20 ` Peter Zijlstra
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 ` [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 ` [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 ` [PATCH v2 10/11] Documentation/locking/ww_mutex: Update the design document 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
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=239fa361-331a-a7b6-9a0d-a6baa19a5003@gmail.com \
--to=nhaehnle@gmail.com \
--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=peterz@infradead.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).