Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jasmine Newsome <jasmine.newsome@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tests/i915/gem_spin_batch: Removing context persistence
Date: Mon, 21 Feb 2022 11:54:48 +0000	[thread overview]
Message-ID: <f2324dc7-4d4e-1e75-a980-9d65276b6d5d@linux.intel.com> (raw)
In-Reply-To: <20220219013215.3531766-3-jasmine.newsome@intel.com>


On 19/02/2022 01:32, Jasmine Newsome wrote:
> The spin all test relied on context persistence unecessarily by trying
> to destroy contexts while keeping spinners active.
> The current implementation of context persistence in i915 can cause
> failures, and persistence is not needed for this test.

Could you please expand a bit on "current implementation" and "can cause 
failures"?

Also from the subject of "Removing context persistence" I was expecting 
to see usage of I915_CONTEXT_PARAM_PERSISTENCE to actually change the mode.

My concern is that the pattern of destroying contexts while keeping 
things active on the GPU is very wide spread in IGT and possibly exists 
in userspace as well.

Has the wider story been analysed by the architects here and what is the 
plan? Do we actually know no userspace actually depends on it?

[Comes back later, after spotting the cover letter.]

So it's only GuC, not i915, so please say that in this commit message 
since cover letters are not saved in git history.

Regards,

Tvrtko

> 
> Moving intel_ctx_destroy after igt_spin_end.
> 
> Signed-off-by: Jasmine Newsome <jasmine.newsome@intel.com>
> ---
>   tests/i915/gem_spin_batch.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/i915/gem_spin_batch.c b/tests/i915/gem_spin_batch.c
> index 653812c7..707d69b6 100644
> --- a/tests/i915/gem_spin_batch.c
> +++ b/tests/i915/gem_spin_batch.c
> @@ -161,8 +161,6 @@ static void spin_all(int i915, const intel_ctx_t *ctx, unsigned int flags)
>   				    .engine = e->flags,
>   				    .flags = (IGT_SPIN_POLL_RUN |
>   					      IGT_SPIN_NO_PREEMPTION));
> -		if (flags & PARALLEL_SPIN_NEW_CTX)
> -			intel_ctx_destroy(i915, ctx);
>   
>   		igt_spin_busywait_until_started(spin);
>   		igt_list_move(&spin->link, &list);
> @@ -172,6 +170,8 @@ static void spin_all(int i915, const intel_ctx_t *ctx, unsigned int flags)
>   		igt_assert(gem_bo_busy(i915, spin->handle));
>   		ahnd = spin->ahnd;
>   		igt_spin_end(spin);
> +		if (flags & PARALLEL_SPIN_NEW_CTX)
> +			intel_ctx_destroy(i915, spin->opts.ctx);
>   		gem_sync(i915, spin->handle);
>   		igt_spin_free(i915, spin);
>   		put_ahnd(ahnd);

  parent reply	other threads:[~2022-02-21 11:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  1:32 [igt-dev] [PATCH i-g-t 0/2] Fix for gem_spin_batch Jasmine Newsome
2022-02-19  1:32 ` [igt-dev] [PATCH i-g-t 1/2] lib/igt_dummyload: Save spin->opts as part of the spinner Jasmine Newsome
2022-02-22 19:49   ` Dixit, Ashutosh
2022-02-19  1:32 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/gem_spin_batch: Removing context persistence Jasmine Newsome
2022-02-19  2:39   ` Dixit, Ashutosh
2022-02-21 11:54   ` Tvrtko Ursulin [this message]
2022-02-23 15:34     ` Newsome, Jasmine
2022-02-19  2:47 ` [igt-dev] ✓ Fi.CI.BAT: success for Fix for gem_spin_batch (rev3) Patchwork
2022-02-19 20:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-02-24  0:42 [igt-dev] [PATCH i-g-t 0/2] Fix for gem_spin_batch Jasmine Newsome
2022-02-24  0:42 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/gem_spin_batch: Removing context persistence Jasmine Newsome
2022-02-24  2:51   ` Dixit, Ashutosh
2022-02-19  0:10 [igt-dev] [PATCH i-g-t 0/2] Fix for gem_spin_batch Jasmine Newsome
2022-02-19  0:10 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/gem_spin_batch: Removing context persistence Jasmine Newsome
2022-02-19  0:20   ` Dixit, Ashutosh

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=f2324dc7-4d4e-1e75-a980-9d65276b6d5d@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jasmine.newsome@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