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: Tue, 16 Apr 2019 15:53:40 +0100	[thread overview]
Message-ID: <3e2fe19b-1282-1597-748a-ac44db2e3e83@linux.intel.com> (raw)
In-Reply-To: <155542424516.25605.17581982610922032964@skylake-alporthouse-com>


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?

Regards,

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

  reply	other threads:[~2019-04-16 14:53 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 [this message]
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
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=3e2fe19b-1282-1597-748a-ac44db2e3e83@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