From: "Siluvery, Arun" <arun.siluvery@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] igt/gem_workarounds: igt to test workaround registers
Date: Wed, 27 Aug 2014 17:17:11 +0100 [thread overview]
Message-ID: <53FE0487.2010607@linux.intel.com> (raw)
In-Reply-To: <20140827155911.GM13629@nuc-i3427.alporthouse.com>
On 27/08/2014 16:59, Chris Wilson wrote:
> On Wed, Aug 27, 2014 at 05:50:16PM +0200, Daniel Vetter wrote:
>> On Tue, Aug 26, 2014 at 02:50:28PM +0100, Arun Siluvery wrote:
>>> Some of the workarounds are lost followed by a gpu reset, suspend/resume;
>>> this patch adds a test which compares register state before and after
>>> the test scenario.
>>>
>>> This test currently verifies only bdw workarounds.
>
> The existing tool didn't need kernel help (other than forcewake). Why
> was that not used as a starting point?
> -Chris
>
Do you mean intel_reg_checker()?
This new test uses kernel help to get the initial state of workarounds
which are exported to debugfs. We could add this known state to the test
itself but Daniel is not ok with that. debugfs part is only added to
support the test.
regards
Arun
next prev parent reply other threads:[~2014-08-27 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 13:50 [PATCH] igt/gem_workarounds: igt to test workaround registers Arun Siluvery
2014-08-27 15:50 ` Daniel Vetter
2014-08-27 15:59 ` Chris Wilson
2014-08-27 16:17 ` Siluvery, Arun [this message]
2014-08-27 16:23 ` Chris Wilson
2014-08-27 17:02 ` Siluvery, Arun
2014-08-27 17:52 ` Chris Wilson
2014-08-27 22:30 ` Damien Lespiau
2014-08-28 5:55 ` Chris Wilson
2014-08-28 6:13 ` Damien Lespiau
2014-08-30 15:22 ` Damien Lespiau
2014-08-30 15:25 ` Damien Lespiau
-- strict thread matches above, loose matches on Subject: below --
2014-08-22 19:42 Arun Siluvery
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=53FE0487.2010607@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@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