From: <paul.gortmaker@windriver.com>
To: Clark Williams <williams@redhat.com>,
Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: <linux-rt-users@vger.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: [PATCH 6.1-rt/5.15-rt 0/1] Backport i915 reset fix from v6.4-rt
Date: Fri, 18 Aug 2023 22:45:24 -0400 [thread overview]
Message-ID: <20230819024525.2056048-1-paul.gortmaker@windriver.com> (raw)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
I'd originally reported an i915 regression caused by a linux-stable
backport, and then later posted an RFC fix for it:
https://lore.kernel.org/linux-rt-users/ZJTuDi1HNp9L2zxY@windriver.com/
That eventually led to further discussion and an eventual fix from
Tvrtko that Sebastian put into the v6.4-rt queue, which is great.
However, the original regression was reported on v5.15-rt. This closes
the loop by backporting the v6.4-rt change to v5.15-rt/v6.1-rt -- as it
turns out, the same backport applies cleanly to both baselines.
The only small change required is to fix up the context a bit in the 5th
and final chunk, because kernel versions before v6.4 dont have the commit
b7d70b8b06ed ("drm/i915/gsc: implement wa 14015076503")
Paul.
--
Cc: Clark Williams <williams@redhat.com> [6.1-rt]
Cc: Joseph Salisbury <joseph.salisbury@canonical.com> [5.15-rt]
---
Tvrtko Ursulin (1):
drm/i915: Do not disable preemption for resets
drivers/gpu/drm/i915/gt/intel_reset.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
--
2.40.0
next reply other threads:[~2023-08-19 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:45 paul.gortmaker [this message]
2023-08-19 2:45 ` [PATCH 1/1] drm/i915: Do not disable preemption for resets paul.gortmaker
2023-08-23 13:39 ` [PATCH 6.1-rt/5.15-rt 0/1] Backport i915 reset fix from v6.4-rt Sebastian Andrzej Siewior
2023-08-23 17:57 ` Joseph Salisbury
2023-10-18 19:58 ` Joseph Salisbury
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=20230819024525.2056048-1-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bigeasy@linutronix.de \
--cc=joseph.salisbury@canonical.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tvrtko.ursulin@intel.com \
--cc=williams@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).