From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: Ramalingam C <ramalingam.c@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Hellstrom Thomas <thomas.hellstrom@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/selftests: Check for incomplete LRI from the context image
Date: Fri, 8 Apr 2022 16:38:02 +0200 [thread overview]
Message-ID: <9f865b14-817f-153e-0bfb-38ca76c25dbd@shipmail.org> (raw)
In-Reply-To: <20220314182005.17071-3-ramalingam.c@intel.com>
On 3/14/22 19:20, Ramalingam C wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
>
> In order to keep the context image parser simple, we assume that all
> commands follow a similar format. A few, especially not MI commands on
> the render engines, have fixed lengths not encoded in a length field.
> This caused us to incorrectly skip over 3D state commands, and start
> interpretting context data as instructions. Eventually, as Daniele
interpreting
> discovered, this would lead us to find addition LRI as part of the data
> and mistakenly add invalid LRI commands to the context probes.
>
> Stop parsing after we see the first !MI command, as we know we will have
> seen all the context registers by that point. (Mostly true for all gen so far,
> though the render context does have LRI after the first page that we
> have been ignoring so far. It would be useful to extract those as well
> so that we have the full list of user accesisble registers.)
accessible
>
> Similarly, emit a warning if we do try to emit an invalid zero-length
> LRI.
>
> Reported-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Acked-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/selftest_lrc.c | 61 +++++++++++++++++++++++---
> 1 file changed, 54 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_lrc.c b/drivers/gpu/drm/i915/gt/selftest_lrc.c
> index 13f57c7c4224..0a8ed4246082 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_lrc.c
> @@ -27,6 +27,9 @@
> #define NUM_GPR 16
> #define NUM_GPR_DW (NUM_GPR * 2) /* each GPR is 2 dwords */
>
> +#define LRI_HEADER MI_INSTR(0x22, 0)
> +#define LRI_LENGTH_MASK GENMASK(7, 0)
> +
> static struct i915_vma *create_scratch(struct intel_gt *gt)
> {
> return __vm_create_scratch_for_read_pinned(>->ggtt->vm, PAGE_SIZE);
> @@ -180,7 +183,7 @@ static int live_lrc_layout(void *arg)
> continue;
> }
>
> - if ((lri & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) {
> + if ((lri & GENMASK(31, 23)) != LRI_HEADER) {
> pr_err("%s: Expected LRI command at dword %d, found %08x\n",
> engine->name, dw, lri);
> err = -EINVAL;
> @@ -945,18 +948,40 @@ store_context(struct intel_context *ce, struct i915_vma *scratch)
> hw = defaults;
> hw += LRC_STATE_OFFSET / sizeof(*hw);
> do {
> - u32 len = hw[dw] & 0x7f;
> + u32 len = hw[dw] & LRI_LENGTH_MASK;
> +
> + /*
> + * Keep it simple, skip parsing complex commands
> + *
> + * At present, there are no more MI_LOAD_REGISTER_IMM
> + * commands after the first 3D state command. Rather
> + * than include a table (see i915_cmd_parser.c) of all
> + * the possible commands and their instruction lengths
> + * (or mask for variable length instructions), assume
> + * we have gathered the complete list of registers and
> + * bail out.
> + */
> + if ((hw[dw] >> INSTR_CLIENT_SHIFT) != INSTR_MI_CLIENT)
> + break;
>
> if (hw[dw] == 0) {
> dw++;
> continue;
> }
>
> - if ((hw[dw] & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) {
> + if ((hw[dw] & GENMASK(31, 23)) != LRI_HEADER) {
> + /* Assume all other MI commands match LRI length mask */
> dw += len + 2;
> continue;
> }
>
> + if (!len) {
> + pr_err("%s: invalid LRI found in context image\n",
> + ce->engine->name);
> + igt_hexdump(defaults, PAGE_SIZE);
> + break;
> + }
> +
> dw++;
> len = (len + 1) / 2;
> while (len--) {
> @@ -1108,18 +1133,29 @@ static struct i915_vma *load_context(struct intel_context *ce, u32 poison)
> hw = defaults;
> hw += LRC_STATE_OFFSET / sizeof(*hw);
> do {
> - u32 len = hw[dw] & 0x7f;
> + u32 len = hw[dw] & LRI_LENGTH_MASK;
> +
> + /* For simplicity, break parsing at the first complex command */
> + if ((hw[dw] >> INSTR_CLIENT_SHIFT) != INSTR_MI_CLIENT)
> + break;
>
> if (hw[dw] == 0) {
> dw++;
> continue;
> }
>
> - if ((hw[dw] & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) {
> + if ((hw[dw] & GENMASK(31, 23)) != LRI_HEADER) {
> dw += len + 2;
> continue;
> }
>
> + if (!len) {
> + pr_err("%s: invalid LRI found in context image\n",
> + ce->engine->name);
> + igt_hexdump(defaults, PAGE_SIZE);
> + break;
> + }
> +
> dw++;
> len = (len + 1) / 2;
> *cs++ = MI_LOAD_REGISTER_IMM(len);
> @@ -1248,18 +1284,29 @@ static int compare_isolation(struct intel_engine_cs *engine,
> hw = defaults;
> hw += LRC_STATE_OFFSET / sizeof(*hw);
> do {
> - u32 len = hw[dw] & 0x7f;
> + u32 len = hw[dw] & LRI_LENGTH_MASK;
> +
> + /* For simplicity, break parsing at the first complex command */
> + if ((hw[dw] >> INSTR_CLIENT_SHIFT) != INSTR_MI_CLIENT)
> + break;
>
> if (hw[dw] == 0) {
> dw++;
> continue;
> }
>
> - if ((hw[dw] & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) {
> + if ((hw[dw] & GENMASK(31, 23)) != LRI_HEADER) {
> dw += len + 2;
> continue;
> }
>
> + if (!len) {
> + pr_err("%s: invalid LRI found in context image\n",
> + engine->name);
> + igt_hexdump(defaults, PAGE_SIZE);
> + break;
> + }
> +
> dw++;
> len = (len + 1) / 2;
> while (len--) {
next prev parent reply other threads:[~2022-04-08 14:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 18:20 [Intel-gfx] [PATCH 0/4] lrc selftest fixes Ramalingam C
2022-03-14 18:20 ` [Intel-gfx] [PATCH 1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts Ramalingam C
2022-04-08 14:45 ` Thomas Hellström
2022-03-14 18:20 ` [Intel-gfx] [PATCH 2/4] drm/i915/selftests: Check for incomplete LRI from the context image Ramalingam C
2022-04-08 14:38 ` Thomas Hellström (Intel) [this message]
2022-03-14 18:20 ` [Intel-gfx] [PATCH 3/4] drm/i915/selftest: Clear the output buffers before GPU writes Ramalingam C
2022-03-21 23:26 ` [Intel-gfx] [PATCH v2 " Ramalingam C
2022-04-08 14:40 ` [Intel-gfx] [PATCH " Thomas Hellström
2022-03-14 18:20 ` [Intel-gfx] [PATCH 4/4] drm/i915/selftest: Always cancel semaphore on error Ramalingam C
2022-04-08 14:43 ` Thomas Hellström
2022-03-14 20:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for lrc selftest fixes (rev2) Patchwork
2022-03-14 20:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-14 21:18 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-22 2:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for lrc selftest fixes (rev3) Patchwork
2022-03-22 2:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-22 2:23 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 2:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=9f865b14-817f-153e-0bfb-38ca76c25dbd@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@intel.com \
--cc=thomas.hellstrom@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox