From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 17/25] drm/i915/selftests: Fill all the drm_vma_manager holes
Date: Mon, 11 Nov 2019 12:01:54 +0000 [thread overview]
Message-ID: <42e0b52a-bf41-cb4a-cd81-e5c23d56a794@intel.com> (raw)
In-Reply-To: <20191110185806.17413-17-chris@chris-wilson.co.uk>
On 10/11/2019 18:57, Chris Wilson wrote:
> To test mmap_offset_exhaustion, we first have to fill the entire vma
> manager leaving a single page. Don't assume that the vma manager is not
> already fragment, and fill all the holes.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.auld@intel.com>
Why is there anything in vm_addr_space_mm at this point? Just leftovers
from a previous test which have yet to be cleaned up?
> ---
> .../drm/i915/gem/selftests/i915_gem_mman.c | 45 ++++++++++++++-----
> 1 file changed, 33 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> index cabf45b1403f..b307574e3f3b 100644
> --- a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> +++ b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> @@ -607,28 +607,43 @@ static int igt_mmap_offset_exhaustion(void *arg)
> struct drm_i915_private *i915 = arg;
> struct drm_mm *mm = &i915->drm.vma_offset_manager->vm_addr_space_mm;
> struct drm_i915_gem_object *obj;
> - struct drm_mm_node resv, *hole;
> - u64 hole_start, hole_end;
> + struct drm_mm_node *hole, *next;
> int loop, err;
>
> /* Disable background reaper */
> disable_retire_worker(i915);
> GEM_BUG_ON(!i915->gt.awake);
> + intel_gt_retire_requests(&i915->gt);
> + i915_gem_drain_freed_objects(i915);
>
> /* Trim the device mmap space to only a page */
> - memset(&resv, 0, sizeof(resv));
> - drm_mm_for_each_hole(hole, mm, hole_start, hole_end) {
> - resv.start = hole_start;
> - resv.size = hole_end - hole_start - 1; /* PAGE_SIZE units */
> - mmap_offset_lock(i915);
> - err = drm_mm_reserve_node(mm, &resv);
> - mmap_offset_unlock(i915);
> + mmap_offset_lock(i915);
> + loop = 1; /* PAGE_SIZE units */
> + list_for_each_entry_safe(hole, next, &mm->hole_stack, hole_stack) {
> + struct drm_mm_node *resv;
> +
> + resv = kzalloc(sizeof(*resv), GFP_NOWAIT);
> + if (!resv) {
> + err = -ENOMEM;
> + goto out_park;
> + }
> +
> + resv->start = drm_mm_hole_node_start(hole) + loop;
> + resv->size = hole->hole_size - loop;
> + resv->color = -1ul;
> + loop = 0;
Praying that there isn't a one page hole at the start.
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> +
> + pr_debug("Reserving hole [%llx + %llx]\n",
> + resv->start, resv->size);
> +
> + err = drm_mm_reserve_node(mm, resv);
> if (err) {
> pr_err("Failed to trim VMA manager, err=%d\n", err);
kfree(resv);
> goto out_park;
> }
> - break;
> }
> + GEM_BUG_ON(!list_is_singular(&mm->hole_stack));
> + mmap_offset_unlock(i915);
>
> /* Just fits! */
> if (!assert_mmap_offset(i915, PAGE_SIZE, 0)) {
> @@ -685,9 +700,15 @@ static int igt_mmap_offset_exhaustion(void *arg)
>
> out:
> mmap_offset_lock(i915);
> - drm_mm_remove_node(&resv);
> - mmap_offset_unlock(i915);
> out_park:
> + drm_mm_for_each_node_safe(hole, next, mm) {
> + if (hole->color != -1ul)
> + continue;
> +
> + drm_mm_remove_node(hole);
> + kfree(hole);
> + }
> + mmap_offset_unlock(i915);
> restore_retire_worker(i915);
> return err;
> err_obj:
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 17/25] drm/i915/selftests: Fill all the drm_vma_manager holes
Date: Mon, 11 Nov 2019 12:01:54 +0000 [thread overview]
Message-ID: <42e0b52a-bf41-cb4a-cd81-e5c23d56a794@intel.com> (raw)
Message-ID: <20191111120154.fJ2u3WA6scw2KS1v5T6mMJoRw6SgxX3h1Ktq1a5yOio@z> (raw)
In-Reply-To: <20191110185806.17413-17-chris@chris-wilson.co.uk>
On 10/11/2019 18:57, Chris Wilson wrote:
> To test mmap_offset_exhaustion, we first have to fill the entire vma
> manager leaving a single page. Don't assume that the vma manager is not
> already fragment, and fill all the holes.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.auld@intel.com>
Why is there anything in vm_addr_space_mm at this point? Just leftovers
from a previous test which have yet to be cleaned up?
> ---
> .../drm/i915/gem/selftests/i915_gem_mman.c | 45 ++++++++++++++-----
> 1 file changed, 33 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> index cabf45b1403f..b307574e3f3b 100644
> --- a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> +++ b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> @@ -607,28 +607,43 @@ static int igt_mmap_offset_exhaustion(void *arg)
> struct drm_i915_private *i915 = arg;
> struct drm_mm *mm = &i915->drm.vma_offset_manager->vm_addr_space_mm;
> struct drm_i915_gem_object *obj;
> - struct drm_mm_node resv, *hole;
> - u64 hole_start, hole_end;
> + struct drm_mm_node *hole, *next;
> int loop, err;
>
> /* Disable background reaper */
> disable_retire_worker(i915);
> GEM_BUG_ON(!i915->gt.awake);
> + intel_gt_retire_requests(&i915->gt);
> + i915_gem_drain_freed_objects(i915);
>
> /* Trim the device mmap space to only a page */
> - memset(&resv, 0, sizeof(resv));
> - drm_mm_for_each_hole(hole, mm, hole_start, hole_end) {
> - resv.start = hole_start;
> - resv.size = hole_end - hole_start - 1; /* PAGE_SIZE units */
> - mmap_offset_lock(i915);
> - err = drm_mm_reserve_node(mm, &resv);
> - mmap_offset_unlock(i915);
> + mmap_offset_lock(i915);
> + loop = 1; /* PAGE_SIZE units */
> + list_for_each_entry_safe(hole, next, &mm->hole_stack, hole_stack) {
> + struct drm_mm_node *resv;
> +
> + resv = kzalloc(sizeof(*resv), GFP_NOWAIT);
> + if (!resv) {
> + err = -ENOMEM;
> + goto out_park;
> + }
> +
> + resv->start = drm_mm_hole_node_start(hole) + loop;
> + resv->size = hole->hole_size - loop;
> + resv->color = -1ul;
> + loop = 0;
Praying that there isn't a one page hole at the start.
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> +
> + pr_debug("Reserving hole [%llx + %llx]\n",
> + resv->start, resv->size);
> +
> + err = drm_mm_reserve_node(mm, resv);
> if (err) {
> pr_err("Failed to trim VMA manager, err=%d\n", err);
kfree(resv);
> goto out_park;
> }
> - break;
> }
> + GEM_BUG_ON(!list_is_singular(&mm->hole_stack));
> + mmap_offset_unlock(i915);
>
> /* Just fits! */
> if (!assert_mmap_offset(i915, PAGE_SIZE, 0)) {
> @@ -685,9 +700,15 @@ static int igt_mmap_offset_exhaustion(void *arg)
>
> out:
> mmap_offset_lock(i915);
> - drm_mm_remove_node(&resv);
> - mmap_offset_unlock(i915);
> out_park:
> + drm_mm_for_each_node_safe(hole, next, mm) {
> + if (hole->color != -1ul)
> + continue;
> +
> + drm_mm_remove_node(hole);
> + kfree(hole);
> + }
> + mmap_offset_unlock(i915);
> restore_retire_worker(i915);
> return err;
> err_obj:
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-11 12:01 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 18:57 [PATCH 01/25] drm/i915: Protect context while grabbing its name for the request Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 02/25] drm/i915/gem: Embed context/timeline name inside the GEM context Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 11:20 ` Mika Kuoppala
2019-11-11 11:20 ` [Intel-gfx] " Mika Kuoppala
2019-11-10 18:57 ` [PATCH 03/25] drm/i915/gem: Update context name on closing Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 10:47 ` Mika Kuoppala
2019-11-11 10:47 ` [Intel-gfx] " Mika Kuoppala
2019-11-11 10:58 ` Chris Wilson
2019-11-11 10:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 04/25] drm/i915/execlists: Move reset_active() from schedule-out to schedule-in Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 05/25] drm/i915/pmu: "Frequency" is reported as accumulated cycles Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 06/25] drm/i915/userptr: Handle unlocked gup retries Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 07/25] drm/i915: Cancel context if it hangs after it is closed Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 10:54 ` Mika Kuoppala
2019-11-11 10:54 ` [Intel-gfx] " Mika Kuoppala
2019-11-11 11:04 ` Chris Wilson
2019-11-11 11:04 ` [Intel-gfx] " Chris Wilson
2019-11-11 11:25 ` Mika Kuoppala
2019-11-11 11:25 ` [Intel-gfx] " Mika Kuoppala
2019-11-10 18:57 ` [PATCH 08/25] drm/i915: Show guilty context name on GPU reset Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 11:26 ` Mika Kuoppala
2019-11-11 11:26 ` [Intel-gfx] " Mika Kuoppala
2019-11-10 18:57 ` [PATCH 09/25] drm/i915/icl: Refine PG_HYSTERESIS Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 10:59 ` Mika Kuoppala
2019-11-11 10:59 ` [Intel-gfx] " Mika Kuoppala
2019-11-10 18:57 ` [PATCH 10/25] drm/i915/execlists: Reduce barrier on context switch to a wmb() Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 13:19 ` Joonas Lahtinen
2019-11-11 13:19 ` [Intel-gfx] " Joonas Lahtinen
2019-11-10 18:57 ` [PATCH 11/25] drm/i915/gem: Silence sparse for RCU protection inside the constructor Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 12/25] drm/i915/userptr: Try to acquire the page lock around set_page_dirty() Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 13/25] drm/i915: Taint the kernel on dumping the GEM ftrace buffer Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 12:44 ` Joonas Lahtinen
2019-11-11 12:44 ` [Intel-gfx] " Joonas Lahtinen
2019-11-10 18:57 ` [PATCH 14/25] drm/i915/selftests: Exercise parallel blit operations on a single ctx Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 12:10 ` Matthew Auld
2019-11-11 12:10 ` [Intel-gfx] " Matthew Auld
2019-11-10 18:57 ` [PATCH 15/25] drm/i915/selftests: Perform some basic cycle counting of MI ops Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 17:10 ` Matthew Auld
2019-11-11 17:10 ` [Intel-gfx] " Matthew Auld
2019-11-11 17:16 ` Chris Wilson
2019-11-11 17:16 ` [Intel-gfx] " Chris Wilson
2019-11-11 17:20 ` Matthew Auld
2019-11-11 17:20 ` [Intel-gfx] " Matthew Auld
2019-11-10 18:57 ` [PATCH 16/25] drm/i915/selftests: Mock the engine sorting for easy validation Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 17/25] drm/i915/selftests: Fill all the drm_vma_manager holes Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-11 12:01 ` Matthew Auld [this message]
2019-11-11 12:01 ` Matthew Auld
2019-11-11 12:09 ` Chris Wilson
2019-11-11 12:09 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:57 ` [PATCH 18/25] Revert "drm/i915: use a separate context for gpu relocs" Chris Wilson
2019-11-10 18:57 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 19/25] drm/i915: Use a ctor for TYPESAFE_BY_RCU i915_request Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 20/25] drm/i915: Drop GEM context as a direct link from i915_request Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 21/25] drm/i915: Push the use-semaphore marker onto the intel_context Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 22/25] drm/i915: Remove i915->kernel_context Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 23/25] drm/i915: Move i915_gem_init_contexts() earlier Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 24/25] drm/i915/uc: Use an internal buffer for firmware images Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 18:58 ` [PATCH 25/25] drm/i915/gt: Pull GT initialisation under intel_gt_init() Chris Wilson
2019-11-10 18:58 ` [Intel-gfx] " Chris Wilson
2019-11-10 19:20 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/25] drm/i915: Protect context while grabbing its name for the request Patchwork
2019-11-10 19:20 ` [Intel-gfx] " Patchwork
2019-11-10 19:40 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-10 19:40 ` [Intel-gfx] " Patchwork
2019-11-11 15:34 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-11-11 15:34 ` [Intel-gfx] " 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=42e0b52a-bf41-cb4a-cd81-e5c23d56a794@intel.com \
--to=matthew.auld@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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