From: Chris Wilson <chris@chris-wilson.co.uk>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/3] tests/gem_exec_parse: add a register write mask
Date: Fri, 18 May 2018 18:15:24 +0100 [thread overview]
Message-ID: <152666372488.13926.2534050463986711372@mail.alporthouse.com> (raw)
In-Reply-To: <20180518171043.4438-2-lionel.g.landwerlin@intel.com>
Quoting Lionel Landwerlin (2018-05-18 18:10:41)
> Some register are masked (meaning the 16bits are dedicated to identify
> which of the other 16bits have to be taken into account by the
> hardware). This change adds the mask to the write but doesn't take it
> into account in the value comparison assert.
>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-05-18 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 17:10 [igt-dev] [PATCH i-g-t 0/3] intel/gem: test the partial whitelisting of the INSTPM register Lionel Landwerlin
2018-05-18 17:10 ` [igt-dev] [PATCH i-g-t 1/3] tests/gem_exec_parse: add a register write mask Lionel Landwerlin
2018-05-18 17:15 ` Chris Wilson [this message]
2018-05-18 17:10 ` [igt-dev] [PATCH i-g-t 2/3] tests/gem_exec_parse: verify that we allow LRI on INSTPM Lionel Landwerlin
2018-05-18 17:20 ` Chris Wilson
2018-05-18 17:10 ` [igt-dev] [PATCH i-g-t 3/3] test/gem_ctx_isolation: verify INSTPM isolation on Gen7+ Lionel Landwerlin
2018-05-18 17:14 ` Chris Wilson
2018-05-18 17:15 ` Lionel Landwerlin
2018-05-18 18:14 ` [igt-dev] ✓ Fi.CI.BAT: success for intel/gem: test the partial whitelisting of the INSTPM register Patchwork
2018-05-19 3:40 ` [igt-dev] ✓ 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=152666372488.13926.2534050463986711372@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.com \
/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.