From: Thomas Hellstrom <thellstrom@vmware.com>
To: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
ccross@google.com, linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 2/2 with seqcount v3] reservation: add suppport for read-only access using rcu
Date: Tue, 29 Apr 2014 20:55:19 +0200 [thread overview]
Message-ID: <535FF597.8040109@vmware.com> (raw)
In-Reply-To: <535FB808.3060608@canonical.com>
On 04/29/2014 04:32 PM, Maarten Lankhorst wrote:
> op 23-04-14 13:15, Maarten Lankhorst schreef:
>> This adds 4 more functions to deal with rcu.
>>
>> reservation_object_get_fences_rcu() will obtain the list of shared
>> and exclusive fences without obtaining the ww_mutex.
>>
>> reservation_object_wait_timeout_rcu() will wait on all fences of the
>> reservation_object, without obtaining the ww_mutex.
>>
>> reservation_object_test_signaled_rcu() will test if all fences of the
>> reservation_object are signaled without using the ww_mutex.
>>
>> reservation_object_get_excl() is added because touching the fence_excl
>> member directly will trigger a sparse warning.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
>> ---
>> Using seqcount and fixing some lockdep bugs.
>> Changes since v2:
>> - Fix some crashes, remove some unneeded barriers when provided by
>> seqcount writes
>> - Fix code to work correctly with sparse's RCU annotations.
>> - Create a global string for the seqcount lock to make lockdep happy.
>>
>> Can I get this version reviewed? If it looks correct I'll mail the
>> full series
>> because it's intertwined with the TTM conversion to use this code.
> Ping, can anyone review this?
Hi, Maarten.
It's on my todo-list. Been away from office for a while.
/Thomas
next prev parent reply other threads:[~2014-04-29 18:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 14:48 [PATCH 0/2] Updates to fence api Maarten Lankhorst
2014-04-09 14:48 ` Maarten Lankhorst
2014-04-09 14:48 ` [PATCH 1/2] reservation: update api and add some helpers Maarten Lankhorst
2014-04-09 14:48 ` Maarten Lankhorst
2014-04-09 14:49 ` [PATCH 2/2] [RFC] reservation: add suppport for read-only access using rcu Maarten Lankhorst
2014-04-09 14:49 ` Maarten Lankhorst
2014-04-10 8:46 ` Thomas Hellstrom
2014-04-10 8:46 ` Thomas Hellstrom
2014-04-10 10:07 ` Maarten Lankhorst
2014-04-10 10:07 ` Maarten Lankhorst
2014-04-10 11:08 ` Thomas Hellstrom
2014-04-10 11:25 ` Thomas Hellstrom
2014-04-10 11:25 ` Thomas Hellstrom
2014-04-10 15:00 ` [PATCH 2/2] [RFC v2 with seqcount] " Maarten Lankhorst
2014-04-10 15:00 ` Maarten Lankhorst
2014-04-11 8:38 ` Thomas Hellstrom
2014-04-11 8:38 ` Thomas Hellstrom
2014-04-11 9:24 ` Maarten Lankhorst
2014-04-11 9:24 ` Maarten Lankhorst
2014-04-11 10:11 ` Thomas Hellstrom
2014-04-11 10:11 ` Thomas Hellstrom
2014-04-11 18:09 ` Maarten Lankhorst
2014-04-11 18:09 ` Maarten Lankhorst
2014-04-11 19:30 ` Thomas Hellstrom
2014-04-11 19:30 ` Thomas Hellstrom
2014-04-14 7:04 ` Maarten Lankhorst
2014-04-11 19:35 ` Thomas Hellstrom
2014-04-11 19:35 ` Thomas Hellstrom
2014-04-14 7:42 ` Maarten Lankhorst
2014-04-14 7:42 ` Maarten Lankhorst
2014-04-14 7:45 ` Thomas Hellstrom
2014-04-14 7:45 ` Thomas Hellstrom
2014-04-23 11:15 ` [RFC PATCH 2/2 with seqcount v3] " Maarten Lankhorst
2014-04-23 11:15 ` Maarten Lankhorst
2014-04-29 14:32 ` Maarten Lankhorst
2014-04-29 14:32 ` Maarten Lankhorst
2014-04-29 18:55 ` Thomas Hellstrom [this message]
2014-04-29 18:55 ` Thomas Hellstrom
2014-05-19 13:42 ` Thomas Hellstrom
2014-05-19 13:42 ` Thomas Hellstrom
2014-05-19 14:13 ` Maarten Lankhorst
2014-05-19 14:13 ` Maarten Lankhorst
2014-05-19 14:43 ` Thomas Hellstrom
2014-05-19 14:43 ` Thomas Hellstrom
2014-05-20 15:13 ` Thomas Hellstrom
2014-05-20 15:13 ` Thomas Hellstrom
2014-05-20 15:32 ` Maarten Lankhorst
2014-05-20 15:32 ` Maarten Lankhorst
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=535FF597.8040109@vmware.com \
--to=thellstrom@vmware.com \
--cc=ccross@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@canonical.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;
as well as URLs for NNTP newsgroup(s).