From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: intel-gfx@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
stable@vger.kernel.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [Regression] drm/i915: Don't use BAR mappings for ring buffers with LLC alone creates issues in stable kernels
Date: Tue, 21 Mar 2023 08:12:19 +0100 [thread overview]
Message-ID: <ZBlY0yzJsT4k7bRL@kroah.com> (raw)
In-Reply-To: <efc7e85a-a170-ba1b-8746-b00784e81e39@manjaro.org>
On Tue, Mar 21, 2023 at 07:58:44AM +0700, Philip Müller wrote:
> On 20.03.23 20:28, Greg Kroah-Hartman wrote:
> > On Sun, Mar 19, 2023 at 10:01:01AM +0700, Philip Müller wrote:
> > > Have to correct the affected kernels to these: 4.14.310, 4.19.278, 5.4.237,
> > > 5.10.175
> >
> > Please don't top-post :(
> >
> > Anyway, should be fixed in the next round of releases in a few days, if
> > not, please let us know.
> >
> > greg k-h
>
> Hi Greg,
>
> seems the RCs work out. 4.19.279-rc1 and 5.10.176-rc1 were tested by a user
> who had the issue on i915. In 5.15 series the drm patch got reverted. I only
> see "drm/i915: Don't use stolen memory for ring buffers with LLC" there as
> "drm/i915: Don't use BAR mappings for ring buffers with LLC" was reverted
> with 5.15.101.
So is 5.15.y ok or not? Sorry, I could not parse your response here.
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-21 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a1bbe56-4463-d18d-d5a9-d249171a569d@manjaro.org>
[not found] ` <a0be2b31-9e72-1254-978e-570b27abb364@manjaro.org>
2023-03-20 13:28 ` [Intel-gfx] [Regression] drm/i915: Don't use BAR mappings for ring buffers with LLC alone creates issues in stable kernels Greg Kroah-Hartman
2023-03-21 0:58 ` Philip Müller
2023-03-21 7:12 ` Greg Kroah-Hartman [this message]
2023-03-21 12:16 ` Philip Müller
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=ZBlY0yzJsT4k7bRL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=philm@manjaro.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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