From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3] drm/i915: Consolidate TLB invalidation flow
Date: Wed, 15 Feb 2023 08:14:08 +0000 [thread overview]
Message-ID: <6c122e1a-6634-fdbd-005b-abaa390f4656@linux.intel.com> (raw)
In-Reply-To: <983c9904-e9f7-1aa2-fb8c-738ad47195a7@intel.com>
On 02/02/2023 09:39, Andrzej Hajda wrote:
> On 02.02.2023 09:33, Tvrtko Ursulin wrote:
>>
>> On 02/02/2023 07:43, Andrzej Hajda wrote:
>>> On 01.02.2023 17:51, Tvrtko Ursulin wrote:
>>
>> [snip]
>>
>>
>>
>> Btw - do you have any idea why the test is suppressed already?! CI
>> told me BAT was a success...
>
>
> Except this patch, igt@i915_selftest@live@gt_tlb always succeeds[1][2].
> So I guess this is just CI logic which do not trust new tests, sounds
> reasonable. Lets wait few days to see if it changes.
Did another run and it is all still green. Also have another r-b from
Matt now. Okay to merge from your point of view?
Regards,
Tvrtko
> [1]:
> http://gfx-ci.igk.intel.com/cibuglog-ng/results/all?query_key=d3cc1f04e52acd0f911cd54fd855a3f085a40e14
> [2]:
> https://lore.kernel.org/intel-gfx/?q=igt%40i915_selftest%40live%40gt_tlb
>
>
> Regards
> Andrzej
>
>>
>> Regards,
>>
>> Tvrtko
>
next prev parent reply other threads:[~2023-02-15 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:51 [Intel-gfx] [PATCH v3] drm/i915: Consolidate TLB invalidation flow Tvrtko Ursulin
2023-02-01 18:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-02-01 18:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-01 19:49 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-02 7:43 ` [Intel-gfx] [PATCH v3] " Andrzej Hajda
2023-02-02 8:33 ` Tvrtko Ursulin
2023-02-02 9:39 ` Andrzej Hajda
2023-02-15 8:14 ` Tvrtko Ursulin [this message]
2023-02-13 18:44 ` Matt Roper
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=6c122e1a-6634-fdbd-005b-abaa390f4656@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@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