Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Arjun Melkaveri <arjun.melkaveri@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/gem_exec_nop: Resolve missing context id in sequential test
Date: Thu, 26 Aug 2021 10:47:04 -0700	[thread overview]
Message-ID: <874kbcqesn.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20210826062714.4885-1-arjun.melkaveri@intel.com>

On Wed, 25 Aug 2021 23:27:14 -0700, Arjun Melkaveri wrote:
>
> Resolved missing context id in exec buf, for sequential test.
> This was due to context mutation changes that was implemeted in
> gem_exec_nop.

LGTM,

Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

> Signed-off-by: Arjun Melkaveri <arjun.melkaveri@intel.com>
> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
>  tests/i915/gem_exec_nop.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/tests/i915/gem_exec_nop.c b/tests/i915/gem_exec_nop.c
> index 09a0c29e..c435335b 100644
> --- a/tests/i915/gem_exec_nop.c
> +++ b/tests/i915/gem_exec_nop.c
> @@ -749,6 +749,7 @@ static void sequential(int fd, uint32_t handle,
>	execbuf.buffer_count = 2;
>	execbuf.flags |= I915_EXEC_HANDLE_LUT;
>	execbuf.flags |= I915_EXEC_NO_RELOC;
> +	execbuf.rsvd1 = ctx->id;
>	igt_require(__gem_execbuf(fd, &execbuf) == 0);
>
>	if (flags & CONTEXT) {
> --
> 2.25.1
>

      parent reply	other threads:[~2021-08-26 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  6:27 [igt-dev] [PATCH i-g-t] tests/i915/gem_exec_nop: Resolve missing context id in sequential test Arjun Melkaveri
2021-08-26  6:44 ` Ch, Sai Gowtham
2021-08-26  7:23 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-08-26 12:55 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-08-26 17:47 ` Dixit, Ashutosh [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=874kbcqesn.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=arjun.melkaveri@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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