All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH] drm/i915: intel_engine_init_global_seqno() requires atomic kmap
Date: Tue, 21 Mar 2017 09:52:44 +0000	[thread overview]
Message-ID: <20170321095244.GA11338@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <0d1a07dc-cc43-89c8-9b3b-96792c523f08@linux.intel.com>

On Tue, Mar 21, 2017 at 08:29:07AM +0000, Tvrtko Ursulin wrote:
> 
> On 20/03/2017 14:56, Chris Wilson wrote:
> >As intel_engine_init_global_seqno() may be called by
> >nop_submit_request() from inside irq context, we have to use atomic
> >versions of kmap/kunmap. This is rare as this requires using gen8 legacy
> >ringbuffer submission.
> >
> >Reported-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Picked up this and the other gem_eio fix (drm/i915: Protect
intel_engine_wakeup() for call from irq context), thanks.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-03-21  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 14:56 [PATCH] drm/i915: intel_engine_init_global_seqno() requires atomic kmap Chris Wilson
2017-03-20 15:52 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-03-21  8:29 ` [PATCH] " Tvrtko Ursulin
2017-03-21  9:52   ` Chris Wilson [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=20170321095244.GA11338@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@intel.com \
    --cc=tvrtko.ursulin@linux.intel.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 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.