From: "leho@kraav.com" <leho@kraav.com>
To: Martin Wilck <Martin.Wilck@suse.com>
Cc: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
Michal Koutny <MKoutny@suse.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"tiwai@suse.de" <tiwai@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.3-rc3: Frozen graphics with kcompactd migrating i915 pages
Date: Thu, 12 Sep 2019 14:58:51 +0300 [thread overview]
Message-ID: <20190912115851.GD6147@papaya> (raw)
In-Reply-To: <3dcff41048621ff440687dd6691aae31a8647a1e.camel@suse.com>
On Thu, Sep 12, 2019 at 11:23:09AM +0000, Martin Wilck wrote:
>
> There's a considerable risk that many users will start seeing this
> regression when 5.3 is released. I am not aware of a workaround.
>
> Is there an alternative to reverting aa56a292ce62 ("drm/i915/userptr:
> Acquire the page lock around set_page_dirty()")? And if we do, what
> would be the consequences? Would other patches need to be reverted,
> too?
I've been running with revert patch for a couple of days and have not
encountered any kernel warnings thus far, nor any other ill effects that
could be attributed to this locking mechanism.
But I'm far from familiar with these subsystems.
Graphics does not hang anymore.
I've also received developer feedback in private that this really should
be fixed before 5.3 release.
--
Leho Kraav, senior technology & digital marketing architect
next prev parent reply other threads:[~2019-09-12 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 12:41 Martin Wilck
2019-08-09 12:53 ` Chris Wilson
2019-09-10 14:20 ` Leho Kraav
2019-09-12 11:23 ` Martin Wilck
2019-09-12 11:58 ` leho [this message]
2019-09-12 11:59 ` Linus Torvalds
2019-09-12 12:47 ` Chris Wilson
2019-09-12 12:56 ` [PATCH] Revert "drm/i915/userptr: Acquire the page lock around set_page_dirty()" Chris Wilson
2019-09-12 14:39 ` [Intel-gfx] " 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=20190912115851.GD6147@papaya \
--to=leho@kraav.com \
--cc=MKoutny@suse.com \
--cc=Martin.Wilck@suse.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome