From: Chris Wilson <chris@chris-wilson.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Pavel Machek <pavel@ucw.cz>,
airlied@redhat.com, intel-gfx@lists.freedesktop.org,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
kernel list <linux-kernel@vger.kernel.org>,
matthew.auld@intel.com, rodrigo.vivi@intel.com
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com
Subject: Re: Linus, please revert 7dc8f11437: regression in 5.7-rc0, hangs while attempting to run X
Date: Tue, 07 Apr 2020 08:24:27 +0100 [thread overview]
Message-ID: <158624426770.4794.6070200474948860768@build.alporthouse.com> (raw)
In-Reply-To: <20200407072047.GA18532@amd.ucw.cz>
Quoting Pavel Machek (2020-04-07 08:20:47)
>
> On Fri 2020-04-03 15:00:31, Pavel Machek wrote:
> > Hi!
> >
> > 7dc8f1143778a35b190f9413f228b3cf28f67f8d
> >
> > drm/i915/gem: Drop relocation slowpath
> >
> > Since the relocations are no longer performed under a global
> > struct_mutex, or any other lock, that is also held by pagefault handlers,
> > we can relax and allow our fast path to take a fault. As we no longer
> > need to abort the fast path for lock avoidance, we no longer need the
> > slow path handling at all.
> >
> > causes regression on thinkpad x220: instead of starting X, I'm looking
> > at blinking cursor.
> >
> > Reverting the patch on too of 919dce24701f7b3 fixes things for me.
>
> I have received no feedback from patch authors, and I believe we don't
> want to break boot in -rc1 on Intel hardware... so the commit should
> be simply reverted.
Beyond the fix already submitted?
-Chris
next prev parent reply other threads:[~2020-04-07 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 7:20 Linus, please revert 7dc8f11437: regression in 5.7-rc0, hangs while attempting to run X Pavel Machek
2020-04-07 7:24 ` Chris Wilson [this message]
2020-04-07 7:48 ` Pavel Machek
2020-04-10 20:25 ` Linus Torvalds
2020-04-11 7:51 ` Pavel Machek
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=158624426770.4794.6070200474948860768@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=airlied@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.auld@intel.com \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rodrigo.vivi@intel.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).