From: Damien Lespiau <damien.lespiau@intel.com>
To: Arun Siluvery <arun.siluvery@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] igt/gem_workarounds: rework igt to test workaround registers
Date: Mon, 1 Sep 2014 15:12:11 +0100 [thread overview]
Message-ID: <20140901141211.GE1118@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1409578187-2909-3-git-send-email-arun.siluvery@linux.intel.com>
On Mon, Sep 01, 2014 at 02:29:47PM +0100, Arun Siluvery wrote:
> kernel patch that exports w/a data to debugfs is reworked so
> update igt accordingly.
>
> Address review comments from Damien.
> - if kernel is not exposing w/a data instead of failing just skip instead.
> - if the platform is not exposing w/a table then no of workarounds
> applied are 0; we can use this data to skip platform checks.
>
> Signed-off-by: Arun Siluvery <arun.siluvery@linux.intel.com>
> ---
> tests/gem_workarounds.c | 44 +++++++++++++++++++++++---------------------
> 1 file changed, 23 insertions(+), 21 deletions(-)
>
> diff --git a/tests/gem_workarounds.c b/tests/gem_workarounds.c
> index 32156d2..fae4382 100644
> --- a/tests/gem_workarounds.c
> +++ b/tests/gem_workarounds.c
> @@ -62,7 +62,7 @@ int drm_fd;
> uint32_t devid;
> static drm_intel_bufmgr *bufmgr;
> struct intel_batchbuffer *batch;
> -int num_wa_regs;
> +int num_wa_regs = 0;
> struct intel_wa_reg *wa_regs;
>
>
> @@ -153,7 +153,7 @@ static void check_workarounds(enum operation op, int num)
> igt_info("Address\tbefore\t\tafter\t\tw/a mask\tresult\n");
> for (i = 0; i < num; ++i) {
> status = (current_wa[i].value & current_wa[i].mask) !=
> - (wa_regs[i].value & wa_regs[i].mask);
> + wa_regs[i].mask;
Hum. This looks so fishy it can't be right. The heart of the problem is
that you're not clear what a mask or value should be.
To me:
- A mask selects bits
- value is the reference W/A value (containing only the correct bits
for a single W/A, some of those bits can be 0, mask is telling us
which bits we're interested about.
- read(reg) & mask is the W/A value read back from the register
--
Damien
next prev parent reply other threads:[~2014-09-01 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 13:29 [PATCH 0/2] Rework workaround igt Arun Siluvery
2014-09-01 13:29 ` [PATCH 1/2] gem_workarounds: intel_wa_registers is now prefixed with i915 Arun Siluvery
2014-09-01 13:29 ` [PATCH 2/2] igt/gem_workarounds: rework igt to test workaround registers Arun Siluvery
2014-09-01 14:12 ` Damien Lespiau [this message]
2014-09-02 9:18 ` [PATCH v2] " Arun Siluvery
2014-09-02 9:59 ` Damien Lespiau
2014-09-02 11:04 ` Daniel Vetter
2014-09-02 11:12 ` Chris Wilson
2014-09-02 13:22 ` Daniel Vetter
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=20140901141211.GE1118@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=arun.siluvery@linux.intel.com \
--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 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.