All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Ekstrand <jason@jlekstrand.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
	Dave Airlie <airlied@redhat.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 3/7] Revert "i915/gem_exec_reloc: Verify engine isolation"
Date: Wed, 9 Jun 2021 12:59:46 -0500	[thread overview]
Message-ID: <CAOFGe96j_-JDNS5ExyS4hX5X+cW6Qu7UwmxAq0DH52anLM05ZA@mail.gmail.com> (raw)
In-Reply-To: <20210608094020.21598-3-daniel.vetter@ffwll.ch>

On Tue, Jun 8, 2021 at 4:40 AM Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> This reverts commit 9fe244cb751c9d3be0581a943bb9baa8651d8d29.
>
> This validates gpu relocations, which we're about to delete.
>
> Cc: Jason Ekstrand <jason@jlekstrand.net>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  tests/i915/gem_exec_reloc.c | 73 -------------------------------------
>  1 file changed, 73 deletions(-)
>
> diff --git a/tests/i915/gem_exec_reloc.c b/tests/i915/gem_exec_reloc.c
> index efe6e2e02c52..3b200f557b2c 100644
> --- a/tests/i915/gem_exec_reloc.c
> +++ b/tests/i915/gem_exec_reloc.c
> @@ -471,72 +471,6 @@ static void active_spin(int fd, unsigned engine)
>         igt_spin_free(fd, spin);
>  }
>
> -static void others_spin(int i915, unsigned engine)
> -{
> -       struct drm_i915_gem_relocation_entry reloc = {};
> -       struct drm_i915_gem_exec_object2 obj = {
> -               .relocs_ptr = to_user_pointer(&reloc),
> -               .relocation_count = 1,
> -       };
> -       struct drm_i915_gem_execbuffer2 execbuf = {
> -               .buffers_ptr = to_user_pointer(&obj),
> -               .buffer_count = 1,
> -               .flags = engine,
> -       };
> -       const struct intel_execution_engine2 *e;
> -       igt_spin_t *spin = NULL;
> -       uint64_t addr;
> -       int fence;
> -
> -       __for_each_physical_engine(i915, e) {
> -               if (e->flags == engine)
> -                       continue;
> -
> -               if (!spin) {
> -                       spin = igt_spin_new(i915,
> -                                           .engine = e->flags,
> -                                           .flags = IGT_SPIN_FENCE_OUT);
> -                       fence = dup(spin->out_fence);
> -               } else {
> -                       int old_fence;
> -
> -                       spin->execbuf.flags &= ~I915_EXEC_RING_MASK;
> -                       spin->execbuf.flags |= e->flags;
> -                       gem_execbuf_wr(i915, &spin->execbuf);
> -
> -                       old_fence = fence;
> -                       fence = sync_fence_merge(old_fence,
> -                                                spin->execbuf.rsvd2 >> 32);
> -                       close(spin->execbuf.rsvd2 >> 32);
> -                       close(old_fence);
> -               }
> -       }
> -       igt_require(spin);
> -
> -       /* All other engines are busy, let's relocate! */
> -       obj.handle = batch_create(i915);
> -       reloc.target_handle = obj.handle;
> -       reloc.presumed_offset = -1;
> -       reloc.offset = 64;
> -       gem_execbuf(i915, &execbuf);

Does this really depend on async relocs?  The spinners above ensure
that all the OTHER engines are busy and then we try to do something
with a relocation on a fresh BO here.  That should be fine.  We should
be able to place a relocation in a BO as long as that BO isn't busy.
Or am I missing something?

--Jason

> -
> -       /* Verify the relocation took place */
> -       gem_read(i915, obj.handle, 64, &addr, sizeof(addr));
> -       igt_assert_eq_u64(addr, obj.offset);
> -       gem_close(i915, obj.handle);
> -
> -       /* Even if the spinner was harmed in the process */
> -       igt_spin_end(spin);
> -       igt_assert_eq(sync_fence_wait(fence, 200), 0);
> -       igt_assert_neq(sync_fence_status(fence), 0);
> -       if (sync_fence_status(fence) < 0)
> -               igt_warn("Spinner was cancelled, %s\n",
> -                        strerror(-sync_fence_status(fence)));
> -       close(fence);
> -
> -       igt_spin_free(i915, spin);
> -}
> -
>  static bool has_64b_reloc(int fd)
>  {
>         return intel_gen(intel_get_drm_devid(fd)) >= 8;
> @@ -1329,13 +1263,6 @@ igt_main
>                 }
>         }
>
> -       igt_subtest_with_dynamic("basic-spin-others") {
> -               __for_each_physical_engine(fd, e) {
> -                       igt_dynamic_f("%s", e->name)
> -                               others_spin(fd, e->flags);
> -               }
> -       }
> -
>         igt_subtest_with_dynamic("basic-many-active") {
>                 __for_each_physical_engine(fd, e) {
>                         igt_dynamic_f("%s", e->name)
> --
> 2.24.1
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-06-09 17:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  9:40 [igt-dev] [PATCH i-g-t 1/7] tests/gem_exec_reloc: Remove banned tests Daniel Vetter
2021-06-08  9:40 ` [igt-dev] [PATCH i-g-t 2/7] Revert "test/i915/gem_exec_reloc: Restore interclient testings" Daniel Vetter
2021-06-09 17:56   ` Jason Ekstrand
2021-06-14 10:40   ` Arkadiusz Hiler
2021-06-08  9:40 ` [igt-dev] [PATCH i-g-t 3/7] Revert "i915/gem_exec_reloc: Verify engine isolation" Daniel Vetter
2021-06-09 17:59   ` Jason Ekstrand [this message]
2021-06-08  9:40 ` [igt-dev] [PATCH i-g-t 4/7] Revert "i915/gem_exec_reloc: Exercise concurrent relocations" Daniel Vetter
2021-06-09 18:12   ` Jason Ekstrand
2021-06-08  9:40 ` [igt-dev] [PATCH i-g-t 5/7] Revert "i915/gem_exec_reloc: Flood the ring with GPU relocs" Daniel Vetter
2021-06-09 18:05   ` Jason Ekstrand
2021-06-08  9:40 ` [igt-dev] [PATCH i-g-t 6/7] Revert "i915/gem_exec_reloc: Check that relocations do not block" Daniel Vetter
2021-06-09 18:03   ` Jason Ekstrand
2021-06-08  9:40 ` [igt-dev] [PATCH i-g-t 7/7] tests/gem_exec_schedule: Use store_dword_plug again Daniel Vetter
2021-06-08 11:22 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/7] tests/gem_exec_reloc: Remove banned tests Patchwork
2021-06-08 16:02 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-08 19:25 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2021-06-09 17:53   ` Jason Ekstrand
2021-06-08 19:44 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t] tests/gem_exec_reloc: Remove banned tests (rev2) Patchwork
2021-06-08 20:08 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2021-06-09  0:49 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2021-06-08  9:38 [igt-dev] [PATCH i-g-t 1/7] tests/gem_exec_reloc: Remove banned tests Daniel Vetter
2021-06-08  9:38 ` [igt-dev] [PATCH i-g-t 3/7] Revert "i915/gem_exec_reloc: Verify engine isolation" Daniel Vetter
2021-06-07  9:29 [igt-dev] [PATCH i-g-t 1/7] tests/gem_exec_reloc: Remove banned tests Daniel Vetter
2021-06-07  9:29 ` [igt-dev] [PATCH i-g-t 3/7] Revert "i915/gem_exec_reloc: Verify engine isolation" 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=CAOFGe96j_-JDNS5ExyS4hX5X+cW6Qu7UwmxAq0DH52anLM05ZA@mail.gmail.com \
    --to=jason@jlekstrand.net \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=igt-dev@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 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.