All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: mika.kuoppala@intel.com
Subject: Re: Small execbuf coherency fixes
Date: Fri, 12 Aug 2016 13:01:37 +0300	[thread overview]
Message-ID: <1470996097.3709.40.camel@linux.intel.com> (raw)
In-Reply-To: <1470830073-7407-1-git-send-email-chris@chris-wilson.co.uk>

On ke, 2016-08-10 at 12:54 +0100, Chris Wilson wrote:
> Execbuf suffers from a coherency problem which in theory is handled by
> the prepare for direct access implemented by pwrite. The issue being not
> only is that function non-existent (implemented inline for pwrite) it is
> missing a barrier or two.

I already provided review feedback for this series, so after that is
applied I'll proceed to review. Don't forget to CC me.

Regards, Joonas

> -Chris
> 
-- 
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

  parent reply	other threads:[~2016-08-12 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 11:54 Small execbuf coherency fixes Chris Wilson
2016-08-10 11:54 ` [PATCH 1/9] drm/i915: Cache kmap between relocations Chris Wilson
2016-08-10 11:54 ` [PATCH 2/9] drm/i915: Extract i915_gem_obj_prepare_shmem_write() Chris Wilson
2016-08-10 11:54 ` [PATCH 3/9] drm/i915: Before accessing an object via the cpu, flush GTT writes Chris Wilson
2016-08-10 11:54 ` [PATCH 4/9] drm/i915: Wait for writes through the GTT to land before reading back Chris Wilson
2016-08-10 11:54 ` [PATCH 5/9] drm/i915: Pin the pages first in shmem prepare read/write Chris Wilson
2016-08-10 11:54 ` [PATCH 6/9] drm/i915: Tidy up flush cpu/gtt write domains Chris Wilson
2016-08-10 11:54 ` [PATCH 7/9] drm/i915: Refactor execbuffer relocation writing Chris Wilson
2016-08-10 11:54 ` [PATCH 8/9] drm/i915: Fallback to single page GTT mmappings for relocations Chris Wilson
2016-08-10 11:54 ` [PATCH 9/9] drm/i915: Disallow direct CPU access to stolen pages " Chris Wilson
2016-08-10 12:32 ` ✗ Ro.CI.BAT: failure for series starting with [1/9] drm/i915: Cache kmap between relocations Patchwork
2016-08-12 10:01 ` Joonas Lahtinen [this message]
2016-08-12 10:41   ` Small execbuf coherency fixes Chris Wilson

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=1470996097.3709.40.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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.