From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Patchwork <patchwork@emeril.freedesktop.org>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/query: Do not assert engine info rsvd being zero
Date: Wed, 4 Mar 2020 10:38:31 +0000 [thread overview]
Message-ID: <e76afadc-1c32-2802-7db1-ae95e421963b@linux.intel.com> (raw)
In-Reply-To: <158331690823.11744.4175864291424750819@skylake-alporthouse-com>
On 04/03/2020 10:15, Chris Wilson wrote:
> Quoting Patchwork (2020-03-04 10:10:54)
>> == Series Details ==
>>
>> Series: tests/i915/query: Do not assert engine info rsvd being zero
>> URL : https://patchwork.freedesktop.org/series/74250/
>> State : success
>
> Did we do a check to make sure the fields were written? Write a few
> rounds of poison into the struct and make sure the poison isn't returned
> on success. (A few rounds just in case few strike it lucky with the
> poison.) And a pair of redzones to check we don't overwrite the ends (I
> think we did that at least, by placing the pointer next to unmapped
> pages.)
We only have a check for no writes past len, nothing to check these
particular rsvd are actually written to by the kernel. It will clear
them though, contrary to my commit message (!).
If we add some poisoning of the engine array elements themselves, then
we are back to having to fix the test if we extend the amount of data
i915 returns. Unless we think we can choose a value for poison which can
never be a valid something else. Not sure how useful that is. I guess it
is a different approach than trying to figure out the returned data is
valid. Not actually needing to understand the data (and replicate the
logic), but just saying "Yeah it looks like something non-random has
been returned, it's a pass.".
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-03-04 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 9:29 [igt-dev] [PATCH i-g-t] tests/i915/query: Do not assert engine info rsvd being zero Tvrtko Ursulin
2020-03-04 10:10 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-04 10:15 ` Chris Wilson
2020-03-04 10:38 ` Tvrtko Ursulin [this message]
2020-03-04 17:34 ` [igt-dev] [PATCH i-g-t] " Brian Welty
2020-03-05 2:30 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=e76afadc-1c32-2802-7db1-ae95e421963b@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=patchwork@emeril.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