From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruno =?UTF-8?B?UHLDqW1vbnQ=?= Subject: Re: [Patch v3] apple-gmux: lock iGP IO to protect from vgaarb changes Date: Mon, 1 Jun 2015 08:22:27 +0200 Message-ID: <20150601082227.01663ac8@pluto.restena.lu> References: <20150305232038.1873d380@neptune.home> <20150306174254.GB19001@vmdeb7> <20150307011546.0050279d@neptune.home> <20150309225238.0b9ced4e@neptune.home> <20150311223445.6af76f7c@neptune.home> <20150527044749.GB21644@fury.dvhart.com> <20150527081323.35a3cf88@pluto.restena.lu> <20150529163650.GA94698@vmdeb7> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from smtprelay.restena.lu ([158.64.1.62]:48294 "EHLO smtprelay.restena.lu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753064AbbFAGXB (ORCPT ); Mon, 1 Jun 2015 02:23:01 -0400 In-Reply-To: <20150529163650.GA94698@vmdeb7> Sender: platform-driver-x86-owner@vger.kernel.org List-ID: To: Darren Hart Cc: Michael Marineau , Bjorn Helgaas , platform-driver-x86@vger.kernel.org, "linux-kernel@vger.kernel.org" , Petri Hodju , Matthew Garrett , "linux-pci@vger.kernel.org" On Fri, 29 May 2015 18:36:50 +0200 Darren Hart wrote: > > Making sure to lock only the intel GPU when present and especially protecting > > against nvidia driver will be hard if legacy-IO is being processed by a hidden > > device! > > Ugh indeed. Worst case we can special case via dmi strings. Is this Apple device > significantly different from others? Bruno, what are you testing on? I only own a pretty old MacBook Air with just NVIDIA IGP and had to rely on BUG reports and testing from affected users. Not doing anything on apple-gmux when only a single GPU is visible should be easy, but denying any vgaarb operation when Intel IGP is hidden and just discrete GPU present is much harder (if one does not want to risk opening the next can of worms). DMI based special-casing would work but will it uncover the next issue with the same device configured differently? Bruno