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>,
	Daniel Vetter <daniel@ffwll.ch>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Convert WARNs during userptr revoke to SIGBUS
Date: Mon, 12 Oct 2015 11:10:11 +0100	[thread overview]
Message-ID: <20151012101011.GB27629@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20151012093135.GA27629@nuc-i3427.alporthouse.com>

On Mon, Oct 12, 2015 at 10:31:35AM +0100, Chris Wilson wrote:
> We basically need to clone the obj, move the pages and vma over and so
> as the vma die the pages are unreferenced. All new use will be forced to
> call gup and be fine.
> 
> Ok, that smells ok, I'll see how doable that is.

Hmm. If we take the vma-centric driver as granted (i.e. using the vma as the
token when pinning, the vma holds fences etc), the tricky part if that we
don't hold a reference from the pinned vma to the object. pin_display to
the rescue!

Initial sketch:

static struct drm_i915_gem_object *steal_pages(struct drm_i915_gem_object *obj)
{
        struct drm_i915_gem_object *clone;
        struct i915_vma *vma;
        int i;

        BUG_ON(obj->stolen);

        clone = i915_gem_object_alloc(obj->base.dev);
        if (clone == NULL)
                return clone;

        drm_gem_private_object_init(obj->base.dev,
                                    &clone->base,
                                    obj->base.size);
        i915_gem_object_init(clone, obj->ops);

        list_splice_init(&obj->vma_list, &clone->vma_list);
        list_for_each_entry(vma, &clone->vma_list, obj_link)
                vma->obj = clone;

        if (obj->pin_display) {
                clone->pin_display = obj->pin_display;
                while (obj->pin_display--) {
                        drm_gem_object_reference(&clone->base);
                        drm_gem_object_unreference(&obj->base);
                }
        }

        clone->bind_count = obj->bind_count;
        obj->bind_count = 0;
        /* vma_ht / vma_hashed */

        for (i = 0; i < I915_NUM_RINGS; i++) {
                if (obj->last_read[i].request == NULL)
                        continue;

                clone->last_read[i].request = obj->last_read[i].request;
                list_replace_init(&obj->last_read[i].link,
                                  &clone->last_read[i].link);
                clone->flags |= 1 << (i + I915_BO_ACTIVE_SHIFT);
        }
        if (obj->last_write.request) {
                clone->last_write.request = obj->last_write.request;
                list_replace_init(&obj->last_write.link,
                                  &clone->last_write.link);
        }

        clone->dirty = obj->dirty;
        obj->dirty = false;

        clone->tiling_mode = obj->tiling_mode;
        clone->stride = obj->stride;

        clone->pin_display = obj->pin_display;
        obj->pin_display = 0;

        clone->madv = I915_MADV_DONTNEED;
        clone->pages = obj->pages;
        clone->pages_pin_count = obj->pages_pin_count;
        clone->get_page = obj->get_page;
        clone->vmapping = obj->vmapping;
        obj->pages = NULL;
        obj->pages_pin_count = 0;
        obj->vmapping = NULL;

        clone->bit_17 = obj->bit_17;
        obj->bit_17 = NULL;

        i915_gem_release_mmap(obj);

        if (I915_BO_IS_ACTIVE(clone))
                clone->active_reference = true;
        else
                drm_gem_object_unreference(&clone->base);

        return clone;
}

It does have the presumption that we have either an active reference or a
pinned reference.
-Chris

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

  reply	other threads:[~2015-10-12 10:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 20:07 [PATCH] drm/i915: Convert WARNs during userptr revoke to SIGBUS Chris Wilson
2015-09-24 10:23 ` Tvrtko Ursulin
2015-09-24 10:31   ` Chris Wilson
2015-09-24 10:55     ` Tvrtko Ursulin
2015-09-28 13:42 ` Daniel Vetter
2015-09-28 13:52   ` Chris Wilson
2015-09-28 14:14     ` Daniel Vetter
2015-10-08  9:45       ` Tvrtko Ursulin
2015-10-09  7:48         ` Daniel Vetter
2015-10-09  8:40           ` Chris Wilson
2015-10-09  8:55             ` Daniel Vetter
2015-10-09  8:59               ` Chris Wilson
2015-10-09  9:03               ` Tvrtko Ursulin
2015-10-09 17:14                 ` Daniel Vetter
2015-10-09 17:26                   ` Chris Wilson
2015-10-09 18:33                     ` Dave Gordon
2015-10-12  9:06                     ` Tvrtko Ursulin
2015-10-12  9:31                       ` Chris Wilson
2015-10-12 10:10                         ` Chris Wilson [this message]
2015-10-12 12:59                           ` Tvrtko Ursulin
2015-10-13 11:26                         ` Daniel Vetter
2015-10-13 11:44                           ` Chris Wilson
2015-10-13 12:23                             ` Daniel Vetter
2015-10-13 13:09                               ` Chris Wilson
2015-10-13 13:39                                 ` Daniel Vetter

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=20151012101011.GB27629@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --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.