From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_ctx_shared: Use the supplied ring for smoketest
Date: Mon, 04 Nov 2019 17:37:21 +0200 [thread overview]
Message-ID: <87lfsvodou.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20191104152909.21736-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Allow the subtests that want to limit the test to a single engine, to
> limit the test to a single engine.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> tests/i915/gem_ctx_shared.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/gem_ctx_shared.c b/tests/i915/gem_ctx_shared.c
> index 6d8cbcce2..4d9ffafce 100644
> --- a/tests/i915/gem_ctx_shared.c
> +++ b/tests/i915/gem_ctx_shared.c
> @@ -740,8 +740,12 @@ static void smoketest(int i915, unsigned ring, unsigned timeout)
> uint32_t *ptr;
>
> nengine = 0;
> - for_each_physical_engine(e, i915)
> - engines[nengine++] = eb_ring(e);
> + if (ring == -1) {
> + for_each_physical_engine(e, i915)
> + engines[nengine++] = eb_ring(e);
> + } else {
> + engines[nengine++] = ring;
> + }
> igt_require(nengine);
>
> scratch = gem_create(i915, 4096);
> --
> 2.24.0.rc2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-11-04 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 15:29 [igt-dev] [PATCH i-g-t] i915/gem_ctx_shared: Use the supplied ring for smoketest Chris Wilson
2019-11-04 15:37 ` Mika Kuoppala [this message]
2019-11-04 16:18 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-11-04 22:03 ` [igt-dev] ✓ Fi.CI.IGT: " 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=87lfsvodou.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@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