From: Peter Zijlstra <peterz@infradead.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] locking/ww_mutex: cleanup lock->ctx usage in amdgpu
Date: Tue, 20 Feb 2018 13:35:32 +0100 [thread overview]
Message-ID: <20180220123532.GD25314@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180215141944.4332-1-christian.koenig@amd.com>
This really should've been Cc'ed to me.
On Thu, Feb 15, 2018 at 03:19:42PM +0100, Christian König wrote:
> diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h
> index 39fda195bf78..dd580db289e8 100644
> --- a/include/linux/ww_mutex.h
> +++ b/include/linux/ww_mutex.h
> @@ -358,4 +358,21 @@ static inline bool ww_mutex_is_locked(struct ww_mutex *lock)
> return mutex_is_locked(&lock->base);
> }
>
> +/**
> + * ww_mutex_is_owned_by - is the w/w mutex locked by this task in that context
> + * @lock: the mutex to be queried
> + * @task: the task structure to check
> + * @ctx: the w/w acquire context to test
> + *
> + * Returns true if the mutex is locked in the context by the given task, false
> + * otherwise.
> + */
> +static inline bool ww_mutex_is_owned_by(struct ww_mutex *lock,
> + struct task_struct *task,
> + struct ww_acquire_ctx *ctx)
> +{
> + return likely(__mutex_owner(&lock->base) == task) &&
> + READ_ONCE(lock->ctx) == ctx;
> +}
Nak on that interface, that's racy and broken by design.
_______________________________________________
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: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] locking/ww_mutex: cleanup lock->ctx usage in amdgpu
Date: Tue, 20 Feb 2018 13:35:32 +0100 [thread overview]
Message-ID: <20180220123532.GD25314@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180215141944.4332-1-christian.koenig@amd.com>
This really should've been Cc'ed to me.
On Thu, Feb 15, 2018 at 03:19:42PM +0100, Christian König wrote:
> diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h
> index 39fda195bf78..dd580db289e8 100644
> --- a/include/linux/ww_mutex.h
> +++ b/include/linux/ww_mutex.h
> @@ -358,4 +358,21 @@ static inline bool ww_mutex_is_locked(struct ww_mutex *lock)
> return mutex_is_locked(&lock->base);
> }
>
> +/**
> + * ww_mutex_is_owned_by - is the w/w mutex locked by this task in that context
> + * @lock: the mutex to be queried
> + * @task: the task structure to check
> + * @ctx: the w/w acquire context to test
> + *
> + * Returns true if the mutex is locked in the context by the given task, false
> + * otherwise.
> + */
> +static inline bool ww_mutex_is_owned_by(struct ww_mutex *lock,
> + struct task_struct *task,
> + struct ww_acquire_ctx *ctx)
> +{
> + return likely(__mutex_owner(&lock->base) == task) &&
> + READ_ONCE(lock->ctx) == ctx;
> +}
Nak on that interface, that's racy and broken by design.
next prev parent reply other threads:[~2018-02-20 12:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 14:19 [PATCH 1/3] locking/ww_mutex: cleanup lock->ctx usage in amdgpu Christian König
2018-02-15 14:19 ` Christian König
2018-02-15 14:19 ` [PATCH 2/3] drm/ttm: handle already locked BOs during eviction and swapout Christian König
[not found] ` <20180215141944.4332-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-02-15 14:19 ` [PATCH 3/3] drm/ttm: keep BOs reserved until end of eviction Christian König
2018-02-15 14:19 ` Christian König
2018-02-15 20:36 ` [PATCH 1/3] locking/ww_mutex: cleanup lock->ctx usage in amdgpu Alex Deucher
2018-02-15 20:36 ` Alex Deucher
2018-02-19 15:24 ` Daniel Vetter
2018-02-19 15:24 ` Daniel Vetter
[not found] ` <20180219152421.GQ22199-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-02-19 15:41 ` Christian König
2018-02-19 15:41 ` Christian König
[not found] ` <cbfec1ed-d01f-1d4f-c3c0-cc04b93bc58c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-19 16:15 ` Daniel Vetter
2018-02-19 16:15 ` Daniel Vetter
2018-02-19 16:29 ` Christian König
2018-02-19 16:29 ` Christian König
2018-02-19 16:43 ` Daniel Vetter
2018-02-19 16:43 ` Daniel Vetter
[not found] ` <20180219164354.GB22199-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-02-20 9:43 ` Christian König
2018-02-20 9:43 ` Christian König
[not found] ` <f3cef14f-135c-2446-74b5-20e14773b0c4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-20 11:33 ` Daniel Vetter
2018-02-20 11:33 ` Daniel Vetter
[not found] ` <20180220113318.GN22199-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-02-20 12:31 ` Christian König
2018-02-20 12:31 ` Christian König
2018-02-20 12:35 ` Peter Zijlstra [this message]
2018-02-20 12:35 ` Peter Zijlstra
2018-02-20 13:08 ` Christian König
2018-02-20 13:08 ` Christian König
2018-02-20 13:22 ` Peter Zijlstra
2018-02-20 13:22 ` Peter Zijlstra
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=20180220123532.GD25314@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.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 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.