Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Verify the engine workarounds stick on application
Date: Wed, 17 Apr 2019 09:06:24 +0100	[thread overview]
Message-ID: <5d575451-83a2-18be-378a-a0155b8ba1cf@linux.intel.com> (raw)
In-Reply-To: <155548788176.2264.9220225163351872071@skylake-alporthouse-com>


On 17/04/2019 08:58, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-04-17 08:55:26)
>>
>> On 16/04/2019 21:04, Chris Wilson wrote:
>>> Quoting Chris Wilson (2019-04-16 15:59:38)
>>>> Quoting Tvrtko Ursulin (2019-04-16 15:53:40)
>>>>>
>>>>> On 16/04/2019 15:17, Chris Wilson wrote:
>>>>>> Quoting Tvrtko Ursulin (2019-04-16 15:10:25)
>>>>>>>
>>>>>>> On 16/04/2019 14:14, Chris Wilson wrote:
>>>>>>>> Read the engine workarounds back using the GPU after loading the initial
>>>>>>>> context state to verify that we are setting them correctly, and bail if
>>>>>>>> it fails.
>>>>>>>>
>>>>>>>> v2: Break out the verification into its own loop
>>>>>>>>
>>>>>>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>>>>>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>>>>> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>>>>
>>>>>> Now we just have to decide what to do about the +47 icl failures :)
>>>>>> (Or however many it is this time.)
>>>>>
>>>>> I am hardly keeping pace with your patches, let alone looking at the CI
>>>>> results. :I
>>>>>
>>>>> I see BAT success - where to see the failures and what is failing?
>>>>
>>>> Wait for the shards. BAT just happens to have machines that work!
>>>> In the shards we have about a 30% chance (at the last count) of any test
>>>> that reloads the module to trigger a warning.
>>>
>>> With the -EIO if the intel_engines_verify_workaround() failed, we scored
>>> over 500 changes/failures :) With a whole boatload of tests still trying
>>> to use the GPU even when wedged.
>>
>> With -EIO I guess the only option seems to have the ignore verification
>> patch back.
> 
> Even without that, we still get an *ERROR* on every module load and
> reset. So we still end up with a sea of orange for icl.

Yes, no alternative to having that patch, ignore_write_or or what it was 
called.

Retgards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-04-17  8:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 13:14 [PATCH 1/2] drm/i915: Verify workarounds immediately after application Chris Wilson
2019-04-16 13:14 ` [PATCH 2/2] drm/i915: Verify the engine workarounds stick on application Chris Wilson
2019-04-16 14:10   ` Tvrtko Ursulin
2019-04-16 14:17     ` Chris Wilson
2019-04-16 14:53       ` Tvrtko Ursulin
2019-04-16 14:59         ` Chris Wilson
2019-04-16 20:04           ` Chris Wilson
2019-04-17  7:55             ` Tvrtko Ursulin
2019-04-17  7:58               ` Chris Wilson
2019-04-17  8:06                 ` Tvrtko Ursulin [this message]
2019-04-16 14:05 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Verify workarounds immediately after application Patchwork
2019-04-16 19:48 ` ✗ Fi.CI.IGT: 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=5d575451-83a2-18be-378a-a0155b8ba1cf@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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