From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Release the atomic kmap relocation cache around snb GTT w/a
Date: Tue, 13 Feb 2018 13:42:03 +0000 [thread overview]
Message-ID: <40f71e41-2f5e-7eb5-8057-9ff682f25b9b@linux.intel.com> (raw)
In-Reply-To: <20180212211157.24037-1-chris@chris-wilson.co.uk>
On 12/02/2018 21:11, Chris Wilson wrote:
> When we need to rebind the vma into the global GTT for snb, we need to
> drop the current reloc_cache as it will be holding a kmap_atomic() and
> we may need to sleep for i915_vma_bind(). In practice, this is not an
> issue as we already hold an rpm reference for the execbuffer, but with
> tighter error checking around rpm we need to be more careful.
>
> References: 31a39207f04a ("drm/i915: Cache kmap between relocations")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem_execbuffer.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> index b15305f2fb76..8c34b1b5a126 100644
> --- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> +++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> @@ -1315,6 +1315,12 @@ eb_relocate_entry(struct i915_execbuffer *eb,
> */
> if (reloc->write_domain == I915_GEM_DOMAIN_INSTRUCTION &&
> IS_GEN6(eb->i915)) {
> + /*
> + * Release the kmap_atomic cache in order to allow the
> + * i915_vma_bind() to sleep (if needs be).
> + */
> + reloc_cache_reset(&eb->reloc_cache);
> +
> err = i915_vma_bind(target, target->obj->cache_level,
> PIN_GLOBAL);
> if (WARN_ONCE(err,
>
Hmm yes, very interesting. If you are happy with the performance hit then:
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
But in general could it also be solved by changing how
intel_runtime_pm_get works - making our wakeref_count top level and only
calling pm_runtime_get_sync on 0 to 1 transition? That would solve the
issue with proposed might_sleep and code paths which know the condition
is actually impossible.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-13 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 21:11 [PATCH] drm/i915: Release the atomic kmap relocation cache around snb GTT w/a Chris Wilson
2018-02-12 21:56 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-13 0:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-02-13 13:42 ` Tvrtko Ursulin [this message]
2018-02-13 13:45 ` [PATCH] " Chris Wilson
2018-02-13 13:46 ` Chris Wilson
2018-02-13 13:58 ` Tvrtko Ursulin
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=40f71e41-2f5e-7eb5-8057-9ff682f25b9b@linux.intel.com \
--to=tvrtko.ursulin@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