From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Yang, Fei" <fei.yang@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Patchwork <patchwork@emeril.freedesktop.org>
Subject: Re: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: avoid concurrent writes to aux_inv (rev10)
Date: Wed, 30 Mar 2022 16:31:34 +0100 [thread overview]
Message-ID: <74aeae6c-6834-f34f-cdfc-54ee72b1e2f2@linux.intel.com> (raw)
In-Reply-To: <BYAPR11MB2567D70146A33C6FD4D6BCB59A1E9@BYAPR11MB2567.namprd11.prod.outlook.com>
On 29/03/2022 16:59, Yang, Fei wrote:
>> On 29/03/2022 03:30, Patchwork wrote:
>>> *Patch Details*
>>> *Series:* drm/i915: avoid concurrent writes to aux_inv (rev10)
>>> *URL:* https://patchwork.freedesktop.org/series/100772/
>>> <https://patchwork.freedesktop.org/series/100772/>
>>> *State:* success
>>> *Details:*
>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22704/index.html
>>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22704/index.html>
>>>
>>>
>>> CI Bug Log - changes from CI_DRM_11415_full -> Patchwork_22704_full
>>>
>>>
>>> Summary
>>>
>>> *SUCCESS*
>>>
>>> No regressions found.
>>
>> And pushed.
> Thank you so much.
>
>>
>> Does this have any chance of fixing hangs in multiple simultaneous media workloads?
> I hope so. The hang fixed by this patch is pretty easy to reproduce on TGL with two parallel video decoding processes.
Great!
Do you want to send it to stable in this case? Would need to look how
far back it would be easy to backport.
Regards,
Tvrtko
next prev parent reply other threads:[~2022-03-30 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:16 [Intel-gfx] [PATCH] drm/i915: avoid concurrent writes to aux_inv fei.yang
2022-03-28 23:46 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: avoid concurrent writes to aux_inv (rev10) Patchwork
2022-03-29 0:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-29 2:30 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-29 7:54 ` Tvrtko Ursulin
2022-03-29 15:59 ` Yang, Fei
2022-03-30 15:31 ` Tvrtko Ursulin [this message]
2022-03-30 15:37 ` Yang, Fei
2022-03-30 15:50 ` Tvrtko Ursulin
2022-03-29 7:51 ` [Intel-gfx] [PATCH] drm/i915: avoid concurrent writes to aux_inv Tvrtko Ursulin
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=74aeae6c-6834-f34f-cdfc-54ee72b1e2f2@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=fei.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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