From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 03/16] drm/i915: Remove pages_mutex and intel_gtt->vma_ops.set/clear_pages members, v2.
Date: Tue, 7 Dec 2021 11:06:36 +0100 [thread overview]
Message-ID: <efa921e6-2a26-a275-9532-11d8efeb650c@linux.intel.com> (raw)
In-Reply-To: <CAM0jSHMdahtPqwh559wBNitxm=XBm1Mws6F7UEWVrns2Qtxa1g@mail.gmail.com>
On 06-12-2021 18:10, Matthew Auld wrote:
> On Mon, 29 Nov 2021 at 13:57, Maarten Lankhorst
> <maarten.lankhorst@linux.intel.com> wrote:
>> Big delta, but boils down to moving set_pages to i915_vma.c, and removing
>> the special handling, all callers use the defaults anyway. We only remap
>> in ggtt, so default case will fall through.
>>
>> Because we still don't require locking in i915_vma_unpin(), handle this by
>> using xchg in get_pages(), as it's locked with obj->mutex, and cmpxchg in
>> unpin, which only fails if we race a against a new pin.
>>
>> Changes since v1:
>> - aliasing gtt sets ZERO_SIZE_PTR, not -ENODEV, remove special case
>> from __i915_vma_get_pages(). (Matt)
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> <snip>
>
>> +static int
>> +__i915_vma_get_pages(struct i915_vma *vma)
>> +{
>> + struct sg_table *pages;
>> + int ret;
>> +
>> + /*
>> + * The vma->pages are only valid within the lifespan of the borrowed
>> + * obj->mm.pages. When the obj->mm.pages sg_table is regenerated, so
>> + * must be the vma->pages. A simple rule is that vma->pages must only
>> + * be accessed when the obj->mm.pages are pinned.
>> + */
>> + GEM_BUG_ON(!i915_gem_object_has_pinned_pages(vma->obj));
>> +
>> + switch (vma->ggtt_view.type) {
>> + default:
>> + GEM_BUG_ON(vma->ggtt_view.type);
>> + fallthrough;
>> + case I915_GGTT_VIEW_NORMAL:
>> + pages = vma->obj->mm.pages;
>> + break;
>> +
>> + case I915_GGTT_VIEW_ROTATED:
>> + pages =
>> + intel_rotate_pages(&vma->ggtt_view.rotated, vma->obj);
>> + break;
>> +
>> + case I915_GGTT_VIEW_REMAPPED:
>> + pages =
>> + intel_remap_pages(&vma->ggtt_view.remapped, vma->obj);
>> + break;
>> +
>> + case I915_GGTT_VIEW_PARTIAL:
>> + pages = intel_partial_pages(&vma->ggtt_view, vma->obj);
>> + break;
>> + }
>> +
>> + ret = 0;
>> + if (IS_ERR(pages)) {
>> + ret = PTR_ERR(pages);
>> + pages = NULL;
>> + drm_err(&vma->vm->i915->drm,
>> + "Failed to get pages for VMA view type %u (%d)!\n",
>> + vma->ggtt_view.type, ret);
>> + }
>> +
>> + pages = xchg(&vma->pages, pages);
>> +
>> + /* did we race against a put_pages? */
>> + if (pages && pages != vma->obj->mm.pages) {
>> + sg_free_table(vma->pages);
>> + kfree(vma->pages);
> So should this one rather be:
>
> sg_free_table(pages);
> kfree(pages);
>
> Or am I missing something?
Correct! I missed it. Will fix it up when committing, or if a new version is needed.
next prev parent reply other threads:[~2021-12-07 10:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 13:47 [Intel-gfx] [PATCH v2 00/16] drm/i915: Remove short term pins from execbuf Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 01/16] drm/i915: Remove unused bits of i915_vma/active api Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 02/16] drm/i915: Change shrink ordering to use locking around unbinding Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 03/16] drm/i915: Remove pages_mutex and intel_gtt->vma_ops.set/clear_pages members, v2 Maarten Lankhorst
2021-12-06 13:13 ` Matthew Auld
2021-12-06 15:18 ` Maarten Lankhorst
2021-12-06 17:00 ` Matthew Auld
2021-12-07 18:15 ` Daniel Vetter
2021-12-06 17:10 ` Matthew Auld
2021-12-07 10:06 ` Maarten Lankhorst [this message]
2021-12-07 10:45 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 04/16] drm/i915: Take object lock in i915_ggtt_pin if ww is not set Maarten Lankhorst
2021-12-06 13:18 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 05/16] drm/i915: Force ww lock for i915_gem_object_ggtt_pin_ww Maarten Lankhorst
2021-11-30 9:20 ` [Intel-gfx] [PATCH] drm/i915: Force ww lock for i915_gem_object_ggtt_pin_ww, v2 Maarten Lankhorst
2021-12-01 15:07 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 06/16] drm/i915: Ensure gem_contexts selftests work with unbind changes Maarten Lankhorst
2021-12-07 10:44 ` Matthew Auld
2021-12-08 13:20 ` Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 07/16] drm/i915: Take trylock during eviction, v2 Maarten Lankhorst
2021-12-07 11:01 ` Matthew Auld
2021-12-08 13:28 ` Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 08/16] drm/i915: Pass trylock context to callers Maarten Lankhorst
2021-12-07 14:26 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 09/16] drm/i915: Ensure i915_vma tests do not get -ENOSPC with the locking changes Maarten Lankhorst
2021-12-08 11:49 ` Matthew Auld
2021-12-08 12:01 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 10/16] drm/i915: Make i915_gem_evict_vm work correctly for already locked objects Maarten Lankhorst
2021-12-08 12:07 ` Matthew Auld
2021-12-08 13:34 ` Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 11/16] drm/i915: Call i915_gem_evict_vm in vm_fault_gtt to prevent new ENOSPC errors Maarten Lankhorst
2021-12-09 12:17 ` Matthew Auld
2021-12-09 12:59 ` Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 12/16] drm/i915: Add i915_vma_unbind_unlocked, and take obj lock for i915_vma_unbind Maarten Lankhorst
2021-12-09 13:05 ` Matthew Auld
2021-12-09 13:25 ` Maarten Lankhorst
2021-12-09 13:40 ` Matthew Auld
2021-12-09 13:45 ` Maarten Lankhorst
2021-12-09 14:27 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 13/16] drm/i915: Require object lock when freeing pages during destruction Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 14/16] drm/i915: Remove assert_object_held_shared Maarten Lankhorst
2021-12-09 13:07 ` Matthew Auld
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 15/16] drm/i915: Remove support for unlocked i915_vma unbind Maarten Lankhorst
2021-11-29 13:47 ` [Intel-gfx] [PATCH v2 16/16] drm/i915: Remove short-term pins from execbuf, v5 Maarten Lankhorst
2021-12-09 16:22 ` Matthew Auld
2021-11-29 15:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remove short term pins from execbuf Patchwork
2021-11-29 15:33 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-11-29 15:37 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-11-29 16:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-30 8:54 ` [Intel-gfx] [PATCH v2 00/16] " Tvrtko Ursulin
2021-11-30 11:17 ` Maarten Lankhorst
2021-11-30 18:38 ` Tvrtko Ursulin
2021-12-01 11:15 ` Maarten Lankhorst
2021-12-01 13:11 ` Tvrtko Ursulin
2021-11-30 11:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remove short term pins from execbuf. (rev2) Patchwork
2021-11-30 11:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-11-30 11:23 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-11-30 11:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-30 14:51 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=efa921e6-2a26-a275-9532-11d8efeb650c@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.william.auld@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox