Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove toplevel struct_mutex locking from debugfs/i915_drop_caches
Date: Tue, 30 May 2017 11:42:10 +0300	[thread overview]
Message-ID: <1496133730.3977.11.camel@linux.intel.com> (raw)
In-Reply-To: <20170525150314.GR10827@nuc-i3427.alporthouse.com>

On to, 2017-05-25 at 16:03 +0100, Chris Wilson wrote:
> On Thu, May 25, 2017 at 05:58:33PM +0300, Joonas Lahtinen wrote:

<SNIP>

> > 
> > Lock used to work as a serializer, isn't this going to get contended
> > now?
> 
> lockdep_set_current ?
> 
> The intention is to allow the contention to reach i915_gem_shrink where
> we have the more complex locking.

Nevermind,

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

      reply	other threads:[~2017-05-30  8:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 16:26 [PATCH] drm/i915: Remove toplevel struct_mutex locking from debugfs/i915_drop_caches Chris Wilson
2017-05-24 16:44 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-25 14:58 ` [PATCH] " Joonas Lahtinen
2017-05-25 15:03   ` Chris Wilson
2017-05-30  8:42     ` Joonas Lahtinen [this message]

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=1496133730.3977.11.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