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] drm/i915/selftest: Add move poison patterns
Date: Fri, 13 Mar 2020 12:29:16 +0200 [thread overview]
Message-ID: <871rpw1rb7.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200313102812.30173-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Throw in the inverse patterns to create more examples of poison to use
> against the LRC state.
>
> 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>
> ---
> drivers/gpu/drm/i915/gt/selftest_lrc.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_lrc.c b/drivers/gpu/drm/i915/gt/selftest_lrc.c
> index e9e71c52b34d..6f06ba750a0a 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_lrc.c
> @@ -5290,8 +5290,9 @@ static int live_lrc_isolation(void *arg)
> const u32 poison[] = {
> STACK_MAGIC,
> 0x3a3a3a3a,
> - 0xc5c5c5c5,
> + 0x5c5c5c5c,
> 0xffffffff,
> + 0xffff0000,
> };
>
> /*
> @@ -5317,6 +5318,10 @@ static int live_lrc_isolation(void *arg)
> err = __lrc_isolation(engine, poison[i]);
> if (err)
> break;
> +
> + err = __lrc_isolation(engine, ~poison[i]);
> + if (err)
> + break;
> }
> }
> intel_engine_pm_put(engine);
> --
> 2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-13 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 10:28 [Intel-gfx] [PATCH] drm/i915/selftest: Add move poison patterns Chris Wilson
2020-03-13 10:29 ` Mika Kuoppala [this message]
2020-03-13 11:25 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " 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=871rpw1rb7.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;
as well as URLs for NNTP newsgroup(s).