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 i-g-t] tests/i915/i915_hangman: Don't let background contexts cause a ban
Date: Thu, 13 Jan 2022 14:30:47 -0800 [thread overview]
Message-ID: <20220113223047.GA13936@jons-linux-dev-box> (raw)
In-Reply-To: <20220113212653.1554786-1-John.C.Harrison@Intel.com>
On Thu, Jan 13, 2022 at 01:26:53PM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> The global context used by all the subtests for causing hangs is
> marked as unbannable. However, some of the subtests set background
> spinners running on all engines using a freshly created context. If
> there is a test failure for any reason, all of those spinners can be
> killed off as hanging contexts. On systems with lots of engines, that
> can result in the test being banned from creating any new contexts.
>
> So make the spinner contexts unbannable as well. That way if one
> subtest fails it won't necessarily bring down all subsequent subtests.
>
> v2: Simplify anti-banning code (review feedback from Matthew Brost).
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> tests/i915/i915_hangman.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/tests/i915/i915_hangman.c b/tests/i915/i915_hangman.c
> index 9f7f8062c..537ed35a5 100644
> --- a/tests/i915/i915_hangman.c
> +++ b/tests/i915/i915_hangman.c
> @@ -284,6 +284,17 @@ static void test_error_state_capture(const intel_ctx_t *ctx,
> check_alive();
> }
>
> +static void context_unban(int fd, unsigned ctx)
> +{
> + struct drm_i915_gem_context_param param = {
> + .ctx_id = ctx,
> + .param = I915_CONTEXT_PARAM_BANNABLE,
> + .value = 0,
> + };
> +
> + gem_context_set_param(fd, ¶m);
> +}
> +
> static void
> test_engine_hang(const intel_ctx_t *ctx,
> const struct intel_execution_engine2 *e, unsigned int flags)
> @@ -307,6 +318,7 @@ test_engine_hang(const intel_ctx_t *ctx,
> num_ctx = 0;
> for_each_ctx_engine(device, ctx, other) {
> local_ctx[num_ctx] = intel_ctx_create(device, &ctx->cfg);
> + context_unban(device, local_ctx[num_ctx]->id);
> ahndN = get_reloc_ahnd(device, local_ctx[num_ctx]->id);
> spin = __igt_spin_new(device,
> .ahnd = ahndN,
> --
> 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 i-g-t] tests/i915/i915_hangman: Don't let background contexts cause a ban
Date: Thu, 13 Jan 2022 14:30:47 -0800 [thread overview]
Message-ID: <20220113223047.GA13936@jons-linux-dev-box> (raw)
In-Reply-To: <20220113212653.1554786-1-John.C.Harrison@Intel.com>
On Thu, Jan 13, 2022 at 01:26:53PM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> The global context used by all the subtests for causing hangs is
> marked as unbannable. However, some of the subtests set background
> spinners running on all engines using a freshly created context. If
> there is a test failure for any reason, all of those spinners can be
> killed off as hanging contexts. On systems with lots of engines, that
> can result in the test being banned from creating any new contexts.
>
> So make the spinner contexts unbannable as well. That way if one
> subtest fails it won't necessarily bring down all subsequent subtests.
>
> v2: Simplify anti-banning code (review feedback from Matthew Brost).
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> tests/i915/i915_hangman.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/tests/i915/i915_hangman.c b/tests/i915/i915_hangman.c
> index 9f7f8062c..537ed35a5 100644
> --- a/tests/i915/i915_hangman.c
> +++ b/tests/i915/i915_hangman.c
> @@ -284,6 +284,17 @@ static void test_error_state_capture(const intel_ctx_t *ctx,
> check_alive();
> }
>
> +static void context_unban(int fd, unsigned ctx)
> +{
> + struct drm_i915_gem_context_param param = {
> + .ctx_id = ctx,
> + .param = I915_CONTEXT_PARAM_BANNABLE,
> + .value = 0,
> + };
> +
> + gem_context_set_param(fd, ¶m);
> +}
> +
> static void
> test_engine_hang(const intel_ctx_t *ctx,
> const struct intel_execution_engine2 *e, unsigned int flags)
> @@ -307,6 +318,7 @@ test_engine_hang(const intel_ctx_t *ctx,
> num_ctx = 0;
> for_each_ctx_engine(device, ctx, other) {
> local_ctx[num_ctx] = intel_ctx_create(device, &ctx->cfg);
> + context_unban(device, local_ctx[num_ctx]->id);
> ahndN = get_reloc_ahnd(device, local_ctx[num_ctx]->id);
> spin = __igt_spin_new(device,
> .ahnd = ahndN,
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-01-13 22:30 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 ` [igt-dev] " Matthew Brost
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 ` Matthew Brost [this message]
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=20220113223047.GA13936@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.