From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch
Subject: Re: [PATCH igt 2/2] lib: Remove illegal instructions from hang injection
Date: Mon, 07 Aug 2017 16:33:40 +0300 [thread overview]
Message-ID: <87r2wn5wp7.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20170807123636.24907-2-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> The idea behind using an illegal instruction was to hang the GPU must
> faster than simply using the recursive batch. However, we stopped doing
> so on gen8+ as the CS parser was much laxer and allowed the illegal
> command through but still interpreted the packet length (jumping over
> the recursive batch buffer start that followed). Sandybridge doesn't
> just hang the GPU when it encounters an illegal command on the BLT
> engine, it hangs the machine. That goes above and beyond testing our
> hangcheck + reset, so remove the deadly instructions.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> lib/igt_gt.c | 25 +++++--------------------
> 1 file changed, 5 insertions(+), 20 deletions(-)
>
> diff --git a/lib/igt_gt.c b/lib/igt_gt.c
> index 6f7daa5e..d5e8b557 100644
> --- a/lib/igt_gt.c
> +++ b/lib/igt_gt.c
> @@ -270,30 +270,15 @@ igt_hang_t igt_hang_ctx(int fd,
>
> memset(b, 0xc5, sizeof(b));
>
> - /*
> - * We emit invalid command to provoke a gpu hang.
> - * If that doesn't work, we do bb start loop.
> - * Note that the bb start aligment is illegal due this.
> - * But hey, we are here to hang the gpu so whatever works.
> - * We skip 0xfffffff on gen9 as it confuses hw in an such a way that
> - * it will skip over the bb start, causing runaway head and
> - * thus much slower hang detection.
> - */
Daydreaming about MI_HALT,
Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
> len = 2;
> - if (intel_gen(intel_get_drm_devid(fd)) >= 8) {
> - b[0] = MI_NOOP;
> + if (intel_gen(intel_get_drm_devid(fd)) >= 8)
> len++;
> - } else {
> - b[0] = 0xffffffff;
> - }
> -
> - b[1] = MI_BATCH_BUFFER_START | (len - 2);
> - b[1+len] = MI_BATCH_BUFFER_END;
> - b[2+len] = MI_NOOP;
> + b[0] = MI_BATCH_BUFFER_START | (len - 2);
> + b[len] = MI_BATCH_BUFFER_END;
> + b[len+1] = MI_NOOP;
> gem_write(fd, exec.handle, 0, b, sizeof(b));
>
> - reloc.offset = 8;
> - reloc.delta = 4;
> + reloc.offset = sizeof(uint32_t);
> reloc.target_handle = exec.handle;
> reloc.read_domains = I915_GEM_DOMAIN_COMMAND;
>
> --
> 2.13.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-07 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 12:36 [PATCH igt 1/2] igt/gem_exec_capture: Wait for batch to execute before triggering reset Chris Wilson
2017-08-07 12:36 ` [PATCH igt 2/2] lib: Remove illegal instructions from hang injection Chris Wilson
2017-08-07 13:33 ` Mika Kuoppala [this message]
2017-08-08 13:25 ` Daniel Vetter
2017-08-07 13:13 ` ✓ Fi.CI.BAT: success for series starting with [Intel-gfx,1/2] igt/gem_exec_capture: Wait for batch to execute before triggering reset 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=87r2wn5wp7.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--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