Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7256809imu; Tue, 22 Jan 2019 03:04:11 -0800 (PST) X-Google-Smtp-Source: ALg8bN5AUYxHhzJANThKklEH1fp9jro+jZQkxn0C064c+Bh4hOteYlzKVjpQJBV9t540EuyilYnB X-Received: by 2002:a65:49cd:: with SMTP id t13mr31856699pgs.376.1548155051791; Tue, 22 Jan 2019 03:04:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548155051; cv=none; d=google.com; s=arc-20160816; b=QmPY+I8Npp5pD6uvNRN97gO4MWpZpqs6/CbOEK1uQOJRo7QdBipUPXFTwOaBVlQxqo TXtKRJECS09t7Clm1COlrrRyUYKNF6Nn4YVnxKqJOTImz+7VwdGDUZUiQ2YVGVJTduI4 P/onrHaH7O1s5DOy9KSaRMldRz4OBqE0pJTLMJCD2aWqSI5BGD4KXwsYbBNDyJlwKUw0 ZzMN06ZZ5VGoI/1AbjDMlBT2SsmkXL+8VOsN8g409pw3+K7jGgzTh7+7ZpXqZmgYiQjg XD1Xgz4X2NtOJu18iCP+jK3gsP4Zh6PmrDOXdBExJbNzzVRH9b86TFsD25hidnmxvtYI 0QeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=hPjM9+2HV7E7+tnmQnhbpv5/CN+UObmvyR9XJDAXQQs=; b=UuE41HCHWowkZ9t26mCuUhsQ2p7atnz4i7IPR28H7mgNzRAkQ5Id6Db3Evv1nKzeTw q0oKI96wL/g9hCpGi8RFU1wX8VVLOy3U017HyQr+Xz3rI8rOpQJDvs3GwJEXlI1JSUjP H6K5GVuuvL2A4Q1Vj6FGpQsIyIGlChGBdAbU+ju6dIkxVS33nQy3ScgAoJd3erxGOdE0 egH9+DPdUpsiyXoQ5ExHTFrR0EJA7IzGlvgx3OLfDmes5kMghg2GLxZLI570DHPVmvqK u+YlUg20XIsqbOHJjgSGzNU9JuSnrqf9F3kQZoGuhoe0W4aUrGI7E8BJ84Alflus1jYR Aprw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w2si9618545pgh.565.2019.01.22.03.03.55; Tue, 22 Jan 2019 03:04:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728052AbfAVLBL (ORCPT + 99 others); Tue, 22 Jan 2019 06:01:11 -0500 Received: from 8bytes.org ([81.169.241.247]:58804 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727048AbfAVLBL (ORCPT ); Tue, 22 Jan 2019 06:01:11 -0500 Received: by theia.8bytes.org (Postfix, from userid 1000) id 8151353D; Tue, 22 Jan 2019 12:01:10 +0100 (CET) Date: Tue, 22 Jan 2019 12:01:09 +0100 From: Joerg Roedel To: Daniel Vetter Cc: Eric Wong , Joonas Lahtinen , David Woodhouse , David Airlie , Jani Nikula , Rodrigo Vivi , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , intel-gfx , dri-devel , Linux Kernel Mailing List Subject: Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx Message-ID: <20190122110109.x3zoynemdl3ysbsn@8bytes.org> References: <20181227114948.ev4b3jte3ubsc5us@dcvr> <154642214920.6261.102817444136744919@jlahtine-desk.ger.corp.intel.com> <20190104010626.e6yqdqkmdcqjepke@dcvr> <154659116310.4596.13613897418163029789@jlahtine-desk.ger.corp.intel.com> <20190118121705.a4usvhnskyblooja@dcvr> <20190122103914.msboylvkor5sb5lq@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, On Tue, Jan 22, 2019 at 11:46:39AM +0100, Daniel Vetter wrote: > Note that the string of platforms which have various issues with iommu > and igfx is very long, thus far we only disabled it where there's no > workaround to stop it from hanging the box, but otherwise left it > enabled. So if we make a policy change to also disable it anywhere > where it doesn't work well (instead of not at all), there's a pile > more platforms to switch. I think its best to just disable iommu for the igfx devices on these platforms. Can you pick up Eric's patch and extend it with the list of affected platforms? Thanks, Joerg