From: Lukas Wunner <lukas@wunner.de>
To: Darren Hart <dvhart@infradead.org>
Cc: Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
Petri Hodju <petrihodju@yahoo.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Bruno Premont <bonbons@linux-vserver.org>,
Andy Ritger <aritger@nvidia.com>,
Ronald Tschalaer <ronald@innovation.ch>,
Wilfried Klaebe <linux-kernel@lebenslange-mailadresse.de>
Subject: Re: [PATCH] Revert "apple-gmux: lock iGP IO to protect from vgaarb changes"
Date: Wed, 31 Jan 2018 20:44:20 +0100 [thread overview]
Message-ID: <20180131194420.GA5409@wunner.de> (raw)
In-Reply-To: <20180131183925.GA8676@fury>
On Wed, Jan 31, 2018 at 10:39:25AM -0800, Darren Hart wrote:
> On Thu, Jan 25, 2018 at 02:38:00PM -0800, Darren Hart wrote:
> > On Wed, Jan 24, 2018 at 07:35:45PM +0100, Lukas Wunner wrote:
> > > Commit 4eebd5a4e726 ("apple-gmux: lock iGP IO to protect from vgaarb
> > > changes") amended this driver's ->probe hook to lock decoding of normal
> > > (non-legacy) I/O space accesses to the integrated GPU on dual-GPU
> > > MacBook Pros. The lock stays in place until the driver is unbound.
> > >
> > ...
> > >
> > > So let's revert commit 4eebd5a4e726 please. Users experiencing the
> > > issue with the proprietary nvidia driver can comment out the above-
> > > quoted problematic code as a workaround (or try updating the BIOS).
> > >
> > > Cc: Petri Hodju <petrihodju@yahoo.com>
> > > Cc: Bjorn Helgaas <bhelgaas@google.com>
> > > Cc: Bruno Prémont <bonbons@linux-vserver.org>
> > > Cc: Andy Ritger <aritger@nvidia.com>
> > > Cc: Ronald Tschalär <ronald@innovation.ch>
> >
> > I presume we'd like to see this applied to linux-stable as well?
>
> I haven't heard back
I did reply to your e-mail on Jan 26, quote:
"Fine by me. Can you add the stable designation when applying or
would you prefer me to respin?"
https://www.spinics.net/lists/platform-driver-x86/msg14690.html
> but from what I've seen in this thread, this appears to me
> to be in need of porting back to stable releases.
> I'm pushing this to testing, and then shortly to for-next, and then to Linus.
> Please let me know if this isn't what everyone is expecting.
WFM, thanks!
Lukas
next prev parent reply other threads:[~2018-01-31 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 18:35 [PATCH] Revert "apple-gmux: lock iGP IO to protect from vgaarb changes" Lukas Wunner
2018-01-25 20:10 ` Wilfried Klaebe
2018-01-25 20:25 ` Lukas Wunner
2018-01-26 18:53 ` Wilfried Klaebe
2018-01-25 22:38 ` Darren Hart
2018-01-26 0:57 ` Lukas Wunner
2018-01-31 18:39 ` Darren Hart
2018-01-31 19:44 ` Lukas Wunner [this message]
2018-02-01 1:31 ` Andy Ritger
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=20180131194420.GA5409@wunner.de \
--to=lukas@wunner.de \
--cc=andy@infradead.org \
--cc=aritger@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bonbons@linux-vserver.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@lebenslange-mailadresse.de \
--cc=petrihodju@yahoo.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ronald@innovation.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.