[igt-dev] ✓ Fi.CI.BAT: success for tests/i915/query: Do not assert engine info rsvd being zero
Tvrtko Ursulin
tvrtko.ursulin at linux.intel.com
Wed Mar 4 10:38:31 UTC 2020
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
More information about the igt-dev
mailing list