From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt] igt/drv_hangman: Use manual error-state generation
Date: Thu, 20 Oct 2016 11:29:05 +0200 [thread overview]
Message-ID: <20161020092905.GS20761@phenom.ffwll.local> (raw)
In-Reply-To: <20161020090739.6009-1-chris@chris-wilson.co.uk>
On Thu, Oct 20, 2016 at 10:07:39AM +0100, Chris Wilson wrote:
> For the basic error state, we only desire that an error state be created
> following a hang. For that purpose, we do not need a real hang (slow
> 6-12s) but can inject one instead (fast <1s).
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Should we instead speed up hangcheck? I think there's lots of value in
making sure not just error dumping, but also hang detection works somewhat
in BAT. Since if it doesn't any attempt at a full run will lead to pretty
serious disasters. And I have this dream that BAT is the gating thing
deciding whether a patch series deserves a complete pre-merge run ;-)
But since this is a controlled enviromnent we could make hangcheck
super-fast at timing out with some debugfs knob. Would probably also help
a lot with speeding up the gazillion of testcases in gem_reset_stats.
-Daniel
> ---
> tests/drv_hangman.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/tests/drv_hangman.c b/tests/drv_hangman.c
> index 953a4c6..bfe5eaf 100644
> --- a/tests/drv_hangman.c
> +++ b/tests/drv_hangman.c
> @@ -32,6 +32,8 @@
> #include <sys/stat.h>
> #include <fcntl.h>
>
> +#include "igt_debugfs.h"
> +
> #ifndef I915_PARAM_CMD_PARSER_VERSION
> #define I915_PARAM_CMD_PARSER_VERSION 28
> #endif
> @@ -166,15 +168,21 @@ static void test_error_state_basic(void)
> {
> int fd;
>
> - fd = drm_open_driver(DRIVER_INTEL);
> -
> clear_error_state();
> assert_error_state_clear();
>
> - submit_hang(fd, I915_EXEC_RENDER);
> + /* Manually trigger a hang by request a reset */
> + fd = igt_debugfs_open("i915_wedged", O_WRONLY);
> + igt_ignore_warn(write(fd, "1\n", 2));
> + close(fd);
> +
> + /* Wait for the error capture and gpu reset to complete */
> + fd = drm_open_driver(DRIVER_INTEL);
> + gem_quiescent_gpu(fd);
> close(fd);
>
> assert_error_state_collected();
> +
> clear_error_state();
> assert_error_state_clear();
> }
> --
> 2.9.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-20 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 9:07 [PATCH igt] igt/drv_hangman: Use manual error-state generation Chris Wilson
2016-10-20 9:29 ` Daniel Vetter [this message]
2016-10-20 9:46 ` Chris Wilson
2016-10-20 10:05 ` Chris Wilson
2016-10-20 13:14 ` Daniel Vetter
2016-10-20 13:22 ` Chris Wilson
2016-10-24 8:24 ` Daniel Vetter
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=20161020092905.GS20761@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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