public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix whitelist selftests with readonly registers
Date: Sat, 29 Jun 2019 17:34:26 +0300	[thread overview]
Message-ID: <157c9960-7c11-ecc0-e4fe-aae1d38d48a2@intel.com> (raw)
In-Reply-To: <20190629131350.31185-1-chris@chris-wilson.co.uk>

Ship it!

On 29/06/2019 16:13, Chris Wilson wrote:
> From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>
> When a register is readonly there is not much we can tell about its
> value (apart from its default value?). This can be covered by tests
> exercising the value of the register from userspace.
>
> For PS_INVOCATION_COUNT we've got the following piglit tests :
>
>     KHR-GL45.pipeline_statistics_query_tests_ARB.functional_fragment_shader_invocations
>
> Vulkan CTS tests :
>
>     dEQP-VK.query_pool.statistics_query.fragment_shader_invocations.*
>
> v2: Use a local to shrink under 80cols.
>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Fixes: 86554f48e511 ("drm/i915/selftests: Verify whitelist of context registers")
> Tested-by: Anuj Phogat <anuj.phogat@gmail.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> Fixes is a bit much, since the test is still very much nerfed and not
> complemented by a test for read-only non-priv registers...
> -Chris
> ---
>   drivers/gpu/drm/i915/gt/selftest_workarounds.c | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_workarounds.c b/drivers/gpu/drm/i915/gt/selftest_workarounds.c
> index f12cb20fe785..b933d831eeb1 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_workarounds.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_workarounds.c
> @@ -926,7 +926,12 @@ check_whitelisted_registers(struct intel_engine_cs *engine,
>   
>   	err = 0;
>   	for (i = 0; i < engine->whitelist.count; i++) {
> -		if (!fn(engine, a[i], b[i], engine->whitelist.list[i].reg))
> +		const struct i915_wa *wa = &engine->whitelist.list[i];
> +
> +		if (i915_mmio_reg_offset(wa->reg) & RING_FORCE_TO_NONPRIV_RD)
> +			continue;
> +
> +		if (!fn(engine, a[i], b[i], wa->reg))
>   			err = -EINVAL;
>   	}
>   


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-29 14:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 12:07 [PATCH v7 0/3] drm/i915: CTS fixes Lionel Landwerlin
2019-06-28 12:07 ` [PATCH v7 1/3] drm/i915: fix whitelist selftests with readonly registers Lionel Landwerlin
2019-06-28 16:28   ` Anuj Phogat
2019-06-29 13:13   ` [PATCH] " Chris Wilson
2019-06-29 14:34     ` Lionel Landwerlin [this message]
2019-07-02 11:14     ` Chris Wilson
2019-06-28 12:07 ` [PATCH v7 2/3] drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT Lionel Landwerlin
2019-07-02 11:13   ` [Intel-gfx] " Chris Wilson
2019-07-02 12:16     ` Mika Kuoppala
2019-06-28 12:07 ` [PATCH v7 3/3] drm/i915/icl: " Lionel Landwerlin
2019-07-02 11:14   ` [Intel-gfx] " Chris Wilson
2019-07-02 12:30   ` Mika Kuoppala
2019-07-02 12:32     ` Lionel Landwerlin
2019-06-28 12:12 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev7) Patchwork
2019-06-28 17:56 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-29  3:33 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-29 13:00   ` Lionel Landwerlin
2019-07-02 11:19     ` Chris Wilson
2019-06-29 13:22 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev8) Patchwork
2019-06-29 14:10 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-29 19:40 ` ✓ Fi.CI.IGT: " 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=157c9960-7c11-ecc0-e4fe-aae1d38d48a2@intel.com \
    --to=lionel.g.landwerlin@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