From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v7 2/3] drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT
Date: Tue, 02 Jul 2019 15:16:17 +0300 [thread overview]
Message-ID: <87zhlw3a3y.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <156206601183.2466.7357010939425742878@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Lionel Landwerlin (2019-06-28 13:07:19)
>> CFL:C0+ changed the status of those registers which are now
>> blacklisted by default.
>>
>> This is breaking a number of CTS tests on GL & Vulkan :
>>
>> KHR-GL45.pipeline_statistics_query_tests_ARB.functional_fragment_shader_invocations (GL)
>>
>> dEQP-VK.query_pool.statistics_query.fragment_shader_invocations.* (Vulkan)
>>
>> v2: Only use one whitelist entry (Lionel)
>
> Bspec: 14091
Sometimes we have optionally used References: BSID#0934 to
mark the workaround. But it feels a tad redudant now.
>> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> Cc: stable@vger.kernel.org
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
next prev parent reply other threads:[~2019-07-02 12:16 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
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 [this message]
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=87zhlw3a3y.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.