From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 1/3] intel-ci: Drop gem_ctx_switch from fast feedback
Date: Mon, 20 Jan 2020 15:50:46 +0200 [thread overview]
Message-ID: <87y2u2p77t.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200120113642.4121605-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Only a couple of tests from gem_ctx_switch are run in BAT, to check we
> have multiple contexts on RCS. It doesn't actually verify the switch,
> just that the execbuf API accepts the context argument.
>
> This test is redundant as actual context switching (and more) is verified by
> live_gem_contexts and live_gt_contexts selftests.
>
> Instead of using the mediocre gem_ctx_switch stress test in BAT, use
> gem_exec_parallel/contexs and gem_exec_parallel/fds as both ensure
s/contexs/contexts
The gem_exec_parallel seems to use new topology api to set the context.
But the aim is to check the context id delivery through rsvd field
into execbuf?
> multiple contexts are supported for simultaneous use, in a fraction of
> the time.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/intel-ci/fast-feedback.testlist | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index 37a92b4e7..f697eb0cf 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -14,8 +14,6 @@ igt@gem_ctx_create@basic-files
> igt@gem_ctx_exec@basic
> igt@gem_ctx_param@basic
> igt@gem_ctx_param@basic-default
> -igt@gem_ctx_switch@legacy-render
> -igt@gem_ctx_switch@rcs0
> igt@gem_exec_basic@basic
> igt@gem_exec_create@basic
> igt@gem_exec_fence@basic-busy-default
> @@ -24,6 +22,8 @@ igt@gem_exec_fence@basic-await-default
> igt@gem_exec_fence@nb-await-default
> igt@gem_exec_gttfill@basic
> igt@gem_exec_parallel@basic
> +igt@gem_exec_parallel@contexts
> +igt@gem_exec_parallel@fds
> igt@gem_exec_store@basic-all
> igt@gem_exec_suspend@basic
> igt@gem_exec_suspend@basic-s0
> --
> 2.25.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-20 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 11:36 [Intel-gfx] [PATCH i-g-t 1/3] intel-ci: Drop gem_ctx_switch from fast feedback Chris Wilson
2020-01-20 11:36 ` [Intel-gfx] [PATCH i-g-t 2/3] intel-ci: Reduce variety of gem_sync in BAT Chris Wilson
2020-01-20 13:55 ` Mika Kuoppala
2020-01-20 11:36 ` [Intel-gfx] [PATCH i-g-t 3/3] intel-ci: Use one ringfull example Chris Wilson
2020-01-20 13:53 ` Mika Kuoppala
2020-01-20 13:50 ` Mika Kuoppala [this message]
2020-01-20 13:57 ` [Intel-gfx] [PATCH i-g-t 1/3] intel-ci: Drop gem_ctx_switch from fast feedback Chris Wilson
2020-01-20 14:02 ` Mika Kuoppala
2020-01-20 22:38 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/3] " 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=87y2u2p77t.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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