From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tests/gem_sync: Use softpin path for no-reloc gens
Date: Fri, 29 Oct 2021 20:55:40 -0700 [thread overview]
Message-ID: <87h7czb1z7.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20211028182322.34133-3-zbigniew.kempczynski@intel.com>
On Thu, 28 Oct 2021 11:23:22 -0700, Zbigniew Kempczyński wrote:
>
> @@ -384,6 +401,8 @@ active_wakeup_ring(int fd, const intel_ctx_t *ctx, unsigned ring,
> int timeout, int wlen)
> {
> struct intel_engine_data ied;
> + uint64_t ahnd0 = get_reloc_ahnd(fd, 0);
> + uint64_t ahnd = get_reloc_ahnd(fd, ctx->id);
>
> ied = list_store_engines(fd, ctx, ring);
> igt_require(ied.nengines);
> @@ -397,8 +416,14 @@ active_wakeup_ring(int fd, const intel_ctx_t *ctx, unsigned ring,
> unsigned long cycles;
> igt_spin_t *spin[2];
>
> + ahnd0 = get_reloc_ahnd(fd, 0);
> + ahnd = get_reloc_ahnd(fd, ctx->id);
> +
> memset(&object, 0, sizeof(object));
> object.handle = gem_create(fd, 4096);
> + object.offset = get_offset(ahnd, object.handle, 4096, 0);
> + if (ahnd)
> + object.offset = EXEC_OBJECT_PINNED;
> gem_write(fd, object.handle, 0, &bbe, sizeof(bbe));
>
> memset(&execbuf, 0, sizeof(execbuf));
> @@ -408,12 +433,14 @@ active_wakeup_ring(int fd, const intel_ctx_t *ctx, unsigned ring,
> execbuf.rsvd1 = ctx->id;
>
> spin[0] = __igt_spin_new(fd,
> + .ahnd = ahnd,
> .engine = execbuf.flags,
> .flags = (IGT_SPIN_POLL_RUN |
> IGT_SPIN_FAST));
> igt_assert(igt_spin_has_poll(spin[0]));
>
> spin[1] = __igt_spin_new(fd,
> + .ahnd = ahnd,
> .engine = execbuf.flags,
> .flags = (IGT_SPIN_POLL_RUN |
> IGT_SPIN_FAST));
> @@ -490,8 +517,13 @@ active_wakeup_ring(int fd, const intel_ctx_t *ctx, unsigned ring,
> igt_spin_free(fd, spin[1]);
> igt_spin_free(fd, spin[0]);
> gem_close(fd, object.handle);
> + put_offset(ahnd, object.handle);
> + put_ahnd(ahnd);
> + put_ahnd(ahnd0);
> }
> igt_waitchildren_timeout(2*timeout, NULL);
> + put_ahnd(ahnd);
> + put_ahnd(ahnd0);
> igt_assert_eq(intel_detect_and_clear_missed_interrupts(fd), 0);
> }
Sorry don't see ahnd0 being used in active_wakeup_ring() above? Rest looks
fine but please let me know about this one issue. Thanks.
next prev parent reply other threads:[~2021-10-30 3:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 18:23 [igt-dev] [PATCH i-g-t 0/2] Change gem_sync to no-reloc Zbigniew Kempczyński
2021-10-28 18:23 ` [igt-dev] [PATCH i-g-t 1/2] tests/gem_sync: Use timeouts definitions instead hardcoded value Zbigniew Kempczyński
2021-10-29 21:32 ` Dixit, Ashutosh
2021-11-02 7:40 ` Zbigniew Kempczyński
2021-10-28 18:23 ` [igt-dev] [PATCH i-g-t 2/2] tests/gem_sync: Use softpin path for no-reloc gens Zbigniew Kempczyński
2021-10-30 3:55 ` Dixit, Ashutosh [this message]
2021-11-02 8:23 ` Zbigniew Kempczyński
2021-10-28 21:11 ` [igt-dev] ✗ Fi.CI.BAT: failure for Change gem_sync to no-reloc Patchwork
2021-10-29 5:02 ` Zbigniew Kempczyński
2021-10-29 6:10 ` Vudum, Lakshminarayana
2021-10-29 5:33 ` Patchwork
2021-10-29 5:53 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2021-10-29 10:27 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-29 10:46 ` Zbigniew Kempczyński
2021-10-29 16:47 ` Vudum, Lakshminarayana
2021-10-29 16:17 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=87h7czb1z7.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox