All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Petri Latvala <petri.latvala@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Use pagecache write to prepopulate shmemfs from pwrite-ioctl
Date: Tue, 7 Mar 2017 10:22:09 +0000	[thread overview]
Message-ID: <20170307102209.GO3201@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20170307095520.s7e6aodeircwbbyo@platvala-desk.ger.corp.intel.com>

On Tue, Mar 07, 2017 at 11:55:20AM +0200, Petri Latvala wrote:
> 
> For the record, manually launched extended test run on SKL
> resulted in:
> 
> commit f88cf1067cc499f4c9236c4e3ff7e410f9cc76d7
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Sat Mar 4 10:35:32 2017 +0000
> 
>     drm/i915: Use pagecache write to prepopulate shmemfs from pwrite-ioctl
> 
> 
> igt@gem_madvise@dontneed-before-exec: pass -> {'fail', 'incomplete'}
That test is expected to fail, that it ever passed is a fluke.
incomplete there should be a failure in the runner? That should quite
happily spot the purged object in execbuf.

> igt@gem_madvise@dontneed-before-pwrite: pass -> fail
Hmm. Here we are relying on shmemfs reporting the write to the truncated
object as invalid. Looks like we need to do the filtering ourselves. It
is not a huge problem as we still prevent any later instantiation of
pages so just a temporary slip. Setting obj->mm.pages = -EFAULT; is
likely a fun solution.
-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-07 10:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  9:29 [PATCH 1/3] drm/i915: Use pagecache write to prepopulate shmemfs from pwrite-ioctl Chris Wilson
2017-03-06  9:29 ` [PATCH 2/3] drm/i915: Wake up all waiters before idling Chris Wilson
2017-03-06 11:02   ` Chris Wilson
2017-03-06 13:47     ` Chris Wilson
2017-03-06  9:29 ` [PATCH 3/3] drm/i915: Take rpm wakelock for releasing the fence on unbind Chris Wilson
2017-03-06 14:03   ` Tvrtko Ursulin
2017-03-06 14:47     ` Chris Wilson
2017-03-06 12:24 ` ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Use pagecache write to prepopulate shmemfs from pwrite-ioctl Patchwork
2017-03-06 12:24 ` [PATCH 1/3] " Tvrtko Ursulin
2017-03-06 12:48   ` Chris Wilson
2017-03-06 13:49     ` Tvrtko Ursulin
2017-03-06 14:14       ` Chris Wilson
2017-03-06 16:32         ` Tvrtko Ursulin
2017-03-06 21:49           ` Chris Wilson
2017-03-07  7:30             ` Tvrtko Ursulin
2017-03-06 19:48 ` Joonas Lahtinen
2017-03-07  9:55 ` Petri Latvala
2017-03-07 10:22   ` Chris Wilson [this message]
2017-03-07 11:46     ` Petri Latvala
2017-03-07 12:02       ` 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=20170307102209.GO3201@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=petri.latvala@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.