Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7244115imu; Tue, 22 Jan 2019 02:50:00 -0800 (PST) X-Google-Smtp-Source: ALg8bN54vpPjDVUc57xlIsezkf6PvDiKzgjFuP8g/0xweGD5ZMYA9+n4bEwEKz0iDOBvF8RkTftb X-Received: by 2002:a62:9f1b:: with SMTP id g27mr32131107pfe.87.1548154200520; Tue, 22 Jan 2019 02:50:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548154200; cv=none; d=google.com; s=arc-20160816; b=STYyGso01rn+/UgXBTgMo41pRcS5sBxKgTewwODlI1hDgwkxYSdFfV6ixS6iG9qmd8 sZcj6PV8TQ3142EGQa4pkGOi/eycVUGl7sjUPveEZ2UiyWLx/q2NXgjP4APmrgAohxgz 7/65qdcNo/rL2L+QpuX3EyFO0D9+ZzFiiDbpUOFFRRrvAgpDzn4ElK421+kEMXx9RVt9 c2bx+aGXWxqJRe81YsCXn4TvxsG8LXToShCo4EGltzR3RPBBLrQg0YkolGQm4n5WgNRF BzeJkLnxPZJvVRL4yqjIzH3YHEDnT0hMm628LhBfoAMfhBMt33Mb2rmzmU421PtQtfX+ Lk1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=eSPrnxQ6dQuliSqyrd4f/WYTHkwSHxqv0f/vECaUqJQ=; b=JJ/gD/l5wEvIhz0l0EFAS6CNSb4xJgS7k8NZR3qsX2LondPyxHOdr+759Z4AUJw5CW ezOwyAnEttvgHWYVkRxuv/RXGw2Yi7/6PPzqqH7wh6SEX9PSL5qutwKGTyhecKRFgrnC PqvcXZZdD4g4U7A2v6FrAJPCoHwCDsKibsiZmGZdNoyh9xrhRgWUEdr26eRKNWr+OQ+x OcWWDRU5A2D/lESdlH0CtiZxc5RVRzYWAuW/aBk1sbVJmIQchlnmPIRz39FAenaZ48YN g+Ea1+azyhfWzEaJZvgWvd7GM1XEPicDLmyCHAJtxyM/XDnPVsfkzuatb6j4bXTbKtb5 Mj8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=GauPpDcr; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n3si14985385plk.328.2019.01.22.02.49.44; Tue, 22 Jan 2019 02:50:00 -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; dkim=pass header.i=@ffwll.ch header.s=google header.b=GauPpDcr; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727885AbfAVKqv (ORCPT + 99 others); Tue, 22 Jan 2019 05:46:51 -0500 Received: from mail-io1-f66.google.com ([209.85.166.66]:43106 "EHLO mail-io1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726530AbfAVKqv (ORCPT ); Tue, 22 Jan 2019 05:46:51 -0500 Received: by mail-io1-f66.google.com with SMTP id b23so18723878ios.10 for ; Tue, 22 Jan 2019 02:46:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eSPrnxQ6dQuliSqyrd4f/WYTHkwSHxqv0f/vECaUqJQ=; b=GauPpDcrl64e4tZmT2X0TaxinL1WLSO/e90XrEAhy6A9K5RdTNcfu2y6p4OQhz7ydv EpDwxsiW0Hd2WiJHPlrJV4XqbqfsDfqHqzHPoCDVh7HuVX6kSu5AUQr2fceY41BWpDqq UlcGOn99RWMG2x1khvkRVV2iTjwiwzt9Pnyyo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eSPrnxQ6dQuliSqyrd4f/WYTHkwSHxqv0f/vECaUqJQ=; b=loCUzpa28UanAbE2MYLR14xxOtQiTqqqqZM1GInMvLitMERqkoifjfdXgQM5l58nH/ +lNYgOnGCBV0hqAK7Dq4EFLF33hPsKXyNumXZqx8wPkTlhER6bMi6wuJ8F+PQn/rqiA1 L4fcAFHrRMyxccWXS5LAJOW6wdMu55kGD+wukWSZEwPojXyxLVVRKDypCmNDztmG9jZZ nvqh85HW7yyHyjTwAb7tycqR5hJ2BQEOujMCceNGv1uYwz504f+ePuMh4j36pYF37rfD GIOSA981wLcAkkbwXwRWWmCeBq4fnIFtcVFdCbgAC6wPbRDq68EQg+KFjWs9uoKZIXhr 04pg== X-Gm-Message-State: AJcUukecc9FQ652jnLVm6h3979TkFiz5rHSAgYwZVqAFXYWwwIU1yo7P hx1Bjk1iBJvZ/7ga/Cq9mzAvjZUYUAT216BQdNXHdQ== X-Received: by 2002:a6b:4001:: with SMTP id k1mr20279439ioa.34.1548154010404; Tue, 22 Jan 2019 02:46:50 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: <20190122103914.msboylvkor5sb5lq@8bytes.org> From: Daniel Vetter Date: Tue, 22 Jan 2019 11:46:39 +0100 Message-ID: Subject: Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx To: Joerg Roedel 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 Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 22, 2019 at 11:39 AM Joerg Roedel wrote: > > On Fri, Jan 18, 2019 at 12:17:05PM +0000, Eric Wong wrote: > > @@ -5411,6 +5411,7 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e20, quirk_iommu_g4x_gfx); > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e30, quirk_iommu_g4x_gfx); > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e40, quirk_iommu_g4x_gfx); > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e90, quirk_iommu_g4x_gfx); > > +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x0044, quirk_iommu_g4x_gfx); > > > > static void quirk_iommu_rwbf(struct pci_dev *dev) > > { > > @@ -5457,7 +5458,6 @@ static void quirk_calpella_no_shadow_gtt(struct pci_dev *dev) > > } > > } > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x0040, quirk_calpella_no_shadow_gtt); > > -DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x0044, quirk_calpella_no_shadow_gtt); > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x0062, quirk_calpella_no_shadow_gtt); > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x006a, quirk_calpella_no_shadow_gtt); > > This seems to make sense to me. Joonas, any comments or objections? This is ironlake, which has a huge iommu hack in the gpu driver to work around hard hangs, which: - causes massive stalls and kills performance - isn't well tested (it's the only one that needs this), so tends to break So if we do this then imo we should: - probably nuke that w/a too (check for needs_idle_maps and all the related stuff in i915_gem_gtt.c) - roll it out for all affected chips (i.e. need to include 0x0040). 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. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch