From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_workarounds: Require GPU resets
Date: Wed, 30 Jan 2019 08:11:05 +0000 [thread overview]
Message-ID: <6bb73a23-1481-30a4-5a33-f818bc737476@linux.intel.com> (raw)
In-Reply-To: <154878824888.22998.3499562493382523423@skylake-alporthouse-com>
On 29/01/2019 18:57, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-01-28 13:47:02)
>>
>> On 28/01/2019 11:23, Chris Wilson wrote:
>>> Check that we are allowed to reset the GPU prior to execution.
>>>
>>> v2: Push the require checking up into a subgroup
>>>
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> ---
>>> tests/i915/gem_workarounds.c | 29 ++++++++++++++++++++++++++---
>>> 1 file changed, 26 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/tests/i915/gem_workarounds.c b/tests/i915/gem_workarounds.c
>>> index 78478ad2c..44e3dce8a 100644
>>> --- a/tests/i915/gem_workarounds.c
>>> +++ b/tests/i915/gem_workarounds.c
>>> @@ -282,9 +282,32 @@ igt_main
>>> }
>>>
>>> for (op = ops; op->name; op++) {
>>> - for (m = modes; m->name; m++) {
>>> - igt_subtest_f("%s%s", op->name, m->name)
>>> - check_workarounds(device, op->op, m->flags);
>>> + igt_subtest_group {
>>> + igt_hang_t hang = {};
>>> +
>>> + igt_fixture {
>>> + switch (op->op) {
>>> + case GPU_RESET:
>>> + hang = igt_allow_hang(device, 0, 0);
>>> + break;
>>> + default:
>>> + break;
>>> + }
>>> + }
>>> +
>>> + for (m = modes; m->name; m++)
>>> + igt_subtest_f("%s%s", op->name, m->name)
>>> + check_workarounds(device, op->op, m->flags);
>>> +
>>> + igt_fixture {
>>> + switch (op->op) {
>>> + case GPU_RESET:
>>> + igt_disallow_hang(device, hang);
>>> + break;
>>> + default:
>>> + break;
>>> + }
>>> + }
>>> }
>>> }
>>> }
>>>
>>
>> Why the verbose switch and not just:
>>
>> it (op->op == GPU_RESET)
>> hand = igt_allow_hang(...)
>
> It matched the lower level and I thought would be easier to extend in
> future.
Okay I guess.
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
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:[~2019-01-30 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 13:06 [igt-dev] [PATCH i-g-t] i915/gem_workarounds: Require GPU resets Chris Wilson
2019-01-27 13:50 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-27 15:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-01-28 11:03 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] " Tvrtko Ursulin
2019-01-28 11:07 ` Chris Wilson
2019-01-28 11:12 ` Chris Wilson
2019-01-28 13:44 ` Tvrtko Ursulin
2019-01-28 13:47 ` Chris Wilson
2019-01-28 11:23 ` [igt-dev] " Chris Wilson
2019-01-28 13:47 ` Tvrtko Ursulin
2019-01-29 18:57 ` [Intel-gfx] " Chris Wilson
2019-01-30 8:11 ` Tvrtko Ursulin [this message]
2019-01-30 9:49 ` [igt-dev] " Chris Wilson
2019-01-28 11:58 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_workarounds: Require GPU resets (rev2) Patchwork
2019-01-28 15:21 ` [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=6bb73a23-1481-30a4-5a33-f818bc737476@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox