From: Matthew Brost <matthew.brost@intel.com>
To: John.C.Harrison@Intel.com
Cc: IGT-Dev@Lists.FreeDesktop.Org, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH v3 i-g-t 08/15] tests/i915/i915_hangman: Add alive-ness test after error capture
Date: Thu, 13 Jan 2022 12:18:55 -0800 [thread overview]
Message-ID: <20220113201854.GA28094@jons-linux-dev-box> (raw)
In-Reply-To: <20220113195947.1536897-9-John.C.Harrison@Intel.com>
On Thu, Jan 13, 2022 at 11:59:40AM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Added a an extra step to the i915_hangman tests to check that the
> system is still alive after the hang and recovery. This submits a
> simple batch to each engine which does a write to memory and checks
> that the write occurred.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Looks good to me but can't help but think this could be a library
function as I really doubt this is the only test where at the end of the
test we want to verify all engines are alive. Something to keep an eye /
do in a follow up.
With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> tests/i915/i915_hangman.c | 59 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/tests/i915/i915_hangman.c b/tests/i915/i915_hangman.c
> index 5a0c9497c..918418760 100644
> --- a/tests/i915/i915_hangman.c
> +++ b/tests/i915/i915_hangman.c
> @@ -48,8 +48,57 @@
> static int device = -1;
> static int sysfs = -1;
>
> +#define OFFSET_ALIVE 10
> +
> IGT_TEST_DESCRIPTION("Tests for hang detection and recovery");
>
> +static void check_alive(void)
> +{
> + const struct intel_execution_engine2 *engine;
> + const intel_ctx_t *ctx;
> + uint32_t scratch, *out;
> + int fd, i = 0;
> + uint64_t ahnd, scratch_addr;
> +
> + fd = drm_open_driver(DRIVER_INTEL);
> + igt_require(gem_class_can_store_dword(fd, 0));
> +
> + ctx = intel_ctx_create_all_physical(fd);
> + ahnd = get_reloc_ahnd(fd, ctx->id);
> + scratch = gem_create(fd, 4096);
> + scratch_addr = get_offset(ahnd, scratch, 4096, 0);
> + out = gem_mmap__wc(fd, scratch, 0, 4096, PROT_WRITE);
> + gem_set_domain(fd, scratch,
> + I915_GEM_DOMAIN_GTT, I915_GEM_DOMAIN_GTT);
> +
> + for_each_physical_engine(fd, engine) {
> + igt_assert_eq_u32(out[i + OFFSET_ALIVE], 0);
> + i++;
> + }
> +
> + i = 0;
> + for_each_ctx_engine(fd, ctx, engine) {
> + if (!gem_class_can_store_dword(fd, engine->class))
> + continue;
> +
> + /* +OFFSET_ALIVE to ensure engine zero doesn't get a false negative */
> + igt_store_word(fd, ahnd, ctx, engine, -1, scratch, scratch_addr,
> + i + OFFSET_ALIVE, i + OFFSET_ALIVE);
> + i++;
> + }
> +
> + gem_set_domain(fd, scratch, I915_GEM_DOMAIN_GTT, 0);
> +
> + while (i--)
> + igt_assert_eq_u32(out[i + OFFSET_ALIVE], i + OFFSET_ALIVE);
> +
> + munmap(out, 4096);
> + gem_close(fd, scratch);
> + put_ahnd(ahnd);
> + intel_ctx_destroy(fd, ctx);
> + close(fd);
> +}
> +
> static bool has_error_state(int dir)
> {
> bool result;
> @@ -231,6 +280,8 @@ static void test_error_state_capture(const intel_ctx_t *ctx,
> check_error_state(e->name, offset, batch);
> munmap(batch, 4096);
> put_ahnd(ahnd);
> +
> + check_alive();
> }
>
> static void
> @@ -289,6 +340,8 @@ test_engine_hang(const intel_ctx_t *ctx,
> put_ahnd(ahndN);
> }
> put_ahnd(ahnd);
> +
> + check_alive();
> }
>
> static int hang_count;
> @@ -321,6 +374,8 @@ static void test_hang_detector(const intel_ctx_t *ctx,
>
> /* Did it work? */
> igt_assert(hang_count == 1);
> +
> + check_alive();
> }
>
> /* This test covers the case where we end up in an uninitialised area of the
> @@ -356,6 +411,8 @@ static void hangcheck_unterminated(const intel_ctx_t *ctx)
> igt_force_gpu_reset(device);
> igt_assert_f(0, "unterminated batch did not trigger a hang!\n");
> }
> +
> + check_alive();
> }
>
> static void do_tests(const char *name, const char *prefix,
> @@ -433,6 +490,8 @@ igt_main
> igt_assert(sysfs != -1);
>
> igt_require(has_error_state(sysfs));
> +
> + gem_require_mmap_wc(device);
> }
>
> igt_describe("Basic error capture");
> --
> 2.25.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Brost <matthew.brost@intel.com>
To: John.C.Harrison@Intel.com
Cc: IGT-Dev@Lists.FreeDesktop.Org, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH v3 i-g-t 08/15] tests/i915/i915_hangman: Add alive-ness test after error capture
Date: Thu, 13 Jan 2022 12:18:55 -0800 [thread overview]
Message-ID: <20220113201854.GA28094@jons-linux-dev-box> (raw)
In-Reply-To: <20220113195947.1536897-9-John.C.Harrison@Intel.com>
On Thu, Jan 13, 2022 at 11:59:40AM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Added a an extra step to the i915_hangman tests to check that the
> system is still alive after the hang and recovery. This submits a
> simple batch to each engine which does a write to memory and checks
> that the write occurred.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Looks good to me but can't help but think this could be a library
function as I really doubt this is the only test where at the end of the
test we want to verify all engines are alive. Something to keep an eye /
do in a follow up.
With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> tests/i915/i915_hangman.c | 59 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/tests/i915/i915_hangman.c b/tests/i915/i915_hangman.c
> index 5a0c9497c..918418760 100644
> --- a/tests/i915/i915_hangman.c
> +++ b/tests/i915/i915_hangman.c
> @@ -48,8 +48,57 @@
> static int device = -1;
> static int sysfs = -1;
>
> +#define OFFSET_ALIVE 10
> +
> IGT_TEST_DESCRIPTION("Tests for hang detection and recovery");
>
> +static void check_alive(void)
> +{
> + const struct intel_execution_engine2 *engine;
> + const intel_ctx_t *ctx;
> + uint32_t scratch, *out;
> + int fd, i = 0;
> + uint64_t ahnd, scratch_addr;
> +
> + fd = drm_open_driver(DRIVER_INTEL);
> + igt_require(gem_class_can_store_dword(fd, 0));
> +
> + ctx = intel_ctx_create_all_physical(fd);
> + ahnd = get_reloc_ahnd(fd, ctx->id);
> + scratch = gem_create(fd, 4096);
> + scratch_addr = get_offset(ahnd, scratch, 4096, 0);
> + out = gem_mmap__wc(fd, scratch, 0, 4096, PROT_WRITE);
> + gem_set_domain(fd, scratch,
> + I915_GEM_DOMAIN_GTT, I915_GEM_DOMAIN_GTT);
> +
> + for_each_physical_engine(fd, engine) {
> + igt_assert_eq_u32(out[i + OFFSET_ALIVE], 0);
> + i++;
> + }
> +
> + i = 0;
> + for_each_ctx_engine(fd, ctx, engine) {
> + if (!gem_class_can_store_dword(fd, engine->class))
> + continue;
> +
> + /* +OFFSET_ALIVE to ensure engine zero doesn't get a false negative */
> + igt_store_word(fd, ahnd, ctx, engine, -1, scratch, scratch_addr,
> + i + OFFSET_ALIVE, i + OFFSET_ALIVE);
> + i++;
> + }
> +
> + gem_set_domain(fd, scratch, I915_GEM_DOMAIN_GTT, 0);
> +
> + while (i--)
> + igt_assert_eq_u32(out[i + OFFSET_ALIVE], i + OFFSET_ALIVE);
> +
> + munmap(out, 4096);
> + gem_close(fd, scratch);
> + put_ahnd(ahnd);
> + intel_ctx_destroy(fd, ctx);
> + close(fd);
> +}
> +
> static bool has_error_state(int dir)
> {
> bool result;
> @@ -231,6 +280,8 @@ static void test_error_state_capture(const intel_ctx_t *ctx,
> check_error_state(e->name, offset, batch);
> munmap(batch, 4096);
> put_ahnd(ahnd);
> +
> + check_alive();
> }
>
> static void
> @@ -289,6 +340,8 @@ test_engine_hang(const intel_ctx_t *ctx,
> put_ahnd(ahndN);
> }
> put_ahnd(ahnd);
> +
> + check_alive();
> }
>
> static int hang_count;
> @@ -321,6 +374,8 @@ static void test_hang_detector(const intel_ctx_t *ctx,
>
> /* Did it work? */
> igt_assert(hang_count == 1);
> +
> + check_alive();
> }
>
> /* This test covers the case where we end up in an uninitialised area of the
> @@ -356,6 +411,8 @@ static void hangcheck_unterminated(const intel_ctx_t *ctx)
> igt_force_gpu_reset(device);
> igt_assert_f(0, "unterminated batch did not trigger a hang!\n");
> }
> +
> + check_alive();
> }
>
> static void do_tests(const char *name, const char *prefix,
> @@ -433,6 +490,8 @@ igt_main
> igt_assert(sysfs != -1);
>
> igt_require(has_error_state(sysfs));
> +
> + gem_require_mmap_wc(device);
> }
>
> igt_describe("Basic error capture");
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-01-13 20:18 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 19:59 [igt-dev] [PATCH v3 i-g-t 00/15] Fixes for i915_hangman and gem_exec_capture John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 01/15] tests/i915/i915_hangman: Add descriptions John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 02/15] lib/hang: Fix igt_require_hang_ring to work with all engines John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 03/15] tests/i915/i915_hangman: Update capture test to use engine structure John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 19:58 ` [Intel-gfx] [igt-dev] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 04/15] tests/i915/i915_hangman: Explicitly test per engine reset vs full GPU reset John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 05/15] tests/i915/i915_hangman: Add uevent test & fix detector John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 06/15] tests/i915/i915_hangman: Use the correct context in hangcheck_unterminated John.C.Harrison
2022-01-13 20:00 ` [igt-dev] " Matthew Brost
2022-01-13 20:00 ` Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 07/15] lib/store: Refactor common store code into helper function John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 20:10 ` [Intel-gfx] [igt-dev] " Matthew Brost
2022-01-13 20:27 ` John Harrison
2022-01-13 20:27 ` [Intel-gfx] " John Harrison
2022-01-13 20:23 ` Matthew Brost
2022-01-13 20:23 ` [Intel-gfx] " Matthew Brost
2022-01-13 20:40 ` John Harrison
2022-01-13 20:40 ` [Intel-gfx] " John Harrison
2022-01-13 20:50 ` [igt-dev] [PATCH i-g-t] " John.C.Harrison
2022-01-13 20:50 ` [Intel-gfx] " John.C.Harrison
2022-01-13 20:53 ` [Intel-gfx] [igt-dev] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 08/15] tests/i915/i915_hangman: Add alive-ness test after error capture John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 20:18 ` Matthew Brost [this message]
2022-01-13 20:18 ` Matthew Brost
2022-01-13 23:24 ` [igt-dev] [PATCH i-g-t] " John.C.Harrison
2022-01-13 23:24 ` [Intel-gfx] " John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 09/15] tests/i915/i915_hangman: Remove reliance on context persistance John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 20:30 ` [igt-dev] " Matthew Brost
2022-01-13 20:30 ` [Intel-gfx] " Matthew Brost
2022-01-13 20:42 ` John Harrison
2022-01-13 20:38 ` Matthew Brost
2022-01-13 20:38 ` [Intel-gfx] " Matthew Brost
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 10/15] tests/i915/i915_hangman: Run background task on all engines John.C.Harrison
2022-01-13 20:48 ` [igt-dev] " Matthew Brost
2022-01-13 20:48 ` Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 11/15] tests/i915/i915_hangman: Don't let background contexts cause a ban John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 21:01 ` [igt-dev] " Matthew Brost
2022-01-13 21:01 ` [Intel-gfx] " Matthew Brost
2022-01-13 21:19 ` John Harrison
2022-01-13 21:19 ` [Intel-gfx] " John Harrison
2022-01-13 21:26 ` [Intel-gfx] [PATCH i-g-t] " John.C.Harrison
2022-01-13 22:30 ` [igt-dev] " Matthew Brost
2022-01-13 22:30 ` Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 12/15] tests/i915/gem_exec_fence: Configure correct context John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 21:06 ` [Intel-gfx] [igt-dev] " Matthew Brost
2022-01-13 21:23 ` John Harrison
2022-01-13 21:23 ` [Intel-gfx] " John Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 13/15] lib/i915: Add helper for non-destructive engine property updates John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 22:33 ` [igt-dev] " Matthew Brost
2022-01-13 22:33 ` [Intel-gfx] " Matthew Brost
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 14/15] tests/i915/i915_hangman: Configure engine properties for quicker hangs John.C.Harrison
2022-01-13 22:38 ` Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 15/15] tests/i915/gem_exec_capture: Restore engines John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] " John.C.Harrison
2022-01-13 23:04 ` [igt-dev] " Matthew Brost
2022-01-13 23:04 ` [Intel-gfx] " Matthew Brost
2022-01-13 22:23 ` [igt-dev] ✗ Fi.CI.BAT: failure for Fixes for i915_hangman and gem_exec_capture (rev6) Patchwork
2022-01-13 22:53 ` Matthew Brost
2022-01-13 23:15 ` John Harrison
2022-01-13 23:25 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Fixes for i915_hangman and gem_exec_capture (rev7) 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=20220113201854.GA28094@jons-linux-dev-box \
--to=matthew.brost@intel.com \
--cc=IGT-Dev@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@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.