From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] tests/gem_exec_capture: adjust the pi subtest
Date: Wed, 6 Jul 2022 08:56:37 +0200 [thread overview]
Message-ID: <1d7ed3c3-5cc9-88c0-83a5-4a8884631425@linux.intel.com> (raw)
In-Reply-To: <20220705104945.118962-1-matthew.auld@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
On 7/5/2022 12:49 PM, Matthew Auld wrote:
> This was broken by the kernel change: 71b1669ea9bd ("drm/i915/uapi:
> tweak error capture on recoverable contexts"). Update the test to use
> non-recoverable context if needed.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/6350
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
> ---
> tests/i915/gem_exec_capture.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/tests/i915/gem_exec_capture.c b/tests/i915/gem_exec_capture.c
> index c2639082..a25f529b 100644
> --- a/tests/i915/gem_exec_capture.c
> +++ b/tests/i915/gem_exec_capture.c
> @@ -721,6 +721,15 @@ static void prioinv(int fd, int dir, const intel_ctx_t *ctx,
>
> ctx2 = intel_ctx_create_all_physical(fd);
> igt_assert(ctx2);
> + if (needs_recoverable_ctx(fd)) {
> + struct drm_i915_gem_context_param param = {
> + .ctx_id = ctx2->id,
> + .param = I915_CONTEXT_PARAM_RECOVERABLE,
> + .value = 0,
> + };
> +
> + gem_context_set_param(fd, ¶m);
> + }
>
> intel_allocator_init();
> /* Reopen the allocator in the new process. */
prev parent reply other threads:[~2022-07-06 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 10:49 [Intel-gfx] [PATCH i-g-t] tests/gem_exec_capture: adjust the pi subtest Matthew Auld
2022-07-06 6:56 ` Das, Nirmoy [this message]
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=1d7ed3c3-5cc9-88c0-83a5-4a8884631425@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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