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 2/3] intel-ci: Reduce variety of gem_sync in BAT
Date: Mon, 20 Jan 2020 15:55:01 +0200 [thread overview]
Message-ID: <87sgkap70q.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200120113642.4121605-2-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Historically, we've had many problems with missed interrupt/seqno
> syndrome and so have focus on testing with gem_sync. However, these
> tests rely on the kernel itself reporting the issue which it no longer
> does. So why the extra variety may impose different timing of execution
> on the HW (and so different interrupt timings which may or may not help
> uncover issues), they do not have any variety in driver coverage. Reduce
> the variety (halving the associated runtime) as they are no more likely
> to spot an issue than multiple runs through BAT.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> tests/intel-ci/fast-feedback.testlist | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index f697eb0cf..8c574d910 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -45,9 +45,6 @@ igt@gem_ringfill@basic-default-forked
> igt@gem_ringfill@basic-default-fd
> igt@gem_sync@basic-all
> igt@gem_sync@basic-each
> -igt@gem_sync@basic-many-each
> -igt@gem_sync@basic-store-all
> -igt@gem_sync@basic-store-each
> igt@gem_tiled_blits@basic
> igt@gem_tiled_fence_blits@basic
> igt@gem_tiled_pread_basic
> --
> 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:55 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 [this message]
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 ` [Intel-gfx] [PATCH i-g-t 1/3] intel-ci: Drop gem_ctx_switch from fast feedback Mika Kuoppala
2020-01-20 13:57 ` 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=87sgkap70q.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