From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/5] drm/i915: Remove superfluous locking around userfault_list
Date: Mon, 17 Oct 2016 10:44:39 +0300 [thread overview]
Message-ID: <1476690279.3081.4.camel@linux.intel.com> (raw)
In-Reply-To: <20161014110548.14888-3-chris@chris-wilson.co.uk>
On pe, 2016-10-14 at 12:05 +0100, Chris Wilson wrote:
> Now that we have reduced the access to the list to either (a) under the
> struct_mutex whilst holding the RPM wakeref (so that concurrent writers to
> the list are serialised by struct_mutex) and (b) under the atomic
> runtime suspend (which cannot run concurrently with any other accessor due
> to the atomic nature of the runtime suspend) we can remove the extra
> locking around the list itself.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-17 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 11:05 [PATCH v2 1/5] drm/i915: Move user fault tracking to a separate list Chris Wilson
2016-10-14 11:05 ` [PATCH v2 2/5] drm/i915: Use RPM as the barrier for controlling user mmap access Chris Wilson
2016-10-14 11:05 ` [PATCH v2 3/5] drm/i915: Remove superfluous locking around userfault_list Chris Wilson
2016-10-17 7:44 ` Joonas Lahtinen [this message]
2016-10-14 11:05 ` [PATCH v2 4/5] drm/i915: Remove RPM sequence checking Chris Wilson
2016-10-14 11:05 ` [PATCH v2 5/5] drm/i915: Move fence cancellation to runtime suspend Chris Wilson
2016-10-14 13:20 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/5] drm/i915: Move user fault tracking to a separate list Patchwork
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=1476690279.3081.4.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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