From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F0CAAC2D0A3 for ; Tue, 3 Nov 2020 09:58:39 +0000 (UTC) Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6DBD721556 for ; Tue, 3 Nov 2020 09:58:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6DBD721556 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id EDE9F86C98; Tue, 3 Nov 2020 09:58:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bxh0SquM8LZa; Tue, 3 Nov 2020 09:58:35 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by whitealder.osuosl.org (Postfix) with ESMTP id AFE0A86C80; Tue, 3 Nov 2020 09:58:35 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id A8FA8C08A1; Tue, 3 Nov 2020 09:58:35 +0000 (UTC) Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 61357C0889 for ; Tue, 3 Nov 2020 09:58:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by silver.osuosl.org (Postfix) with ESMTP id 483EA20507 for ; Tue, 3 Nov 2020 09:58:34 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from silver.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwFxPdX6sQur for ; Tue, 3 Nov 2020 09:58:33 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by silver.osuosl.org (Postfix) with ESMTPS id E094820505 for ; Tue, 3 Nov 2020 09:58:32 +0000 (UTC) IronPort-SDR: ZGlDuEKQA2tS5QVLekDC21tldAzmE2/YYhlLDE7IhNw91rB8HHcsUZjCJNG/lXnTSvitL9BOX3 UumTvrK3guBg== X-IronPort-AV: E=McAfee;i="6000,8403,9793"; a="233196642" X-IronPort-AV: E=Sophos;i="5.77,447,1596524400"; d="scan'208";a="233196642" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Nov 2020 01:58:32 -0800 IronPort-SDR: qXZ3CdVSYmts5JPldn4hVxPQrAnAqM0Gp50/FrVIsGpM55HmGd9I+qH+0dA28fc+ZNECT9313p hjOw5WMKj6fQ== X-IronPort-AV: E=Sophos;i="5.77,447,1596524400"; d="scan'208";a="528363463" Received: from stevenro-mobl.ger.corp.intel.com (HELO localhost) ([10.252.23.13]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Nov 2020 01:58:28 -0800 MIME-Version: 1.0 In-Reply-To: <99a0d1eb-7fde-dff4-225f-92b68fbf7620@linux.intel.com> References: <20200927063437.13988-1-baolu.lu@linux.intel.com> <8bac9e91-36a0-c1d6-a887-4d60567ac75a@linux.intel.com> <3f5694f3-62f9-cc2b-1c2b-f9e99a4788c1@linux.intel.com> <1ce5b94a-38b3-548e-3b1a-a68390b93953@linux.intel.com> <82dab98e-0761-8946-c31c-92f19a0615b4@linux.intel.com> <99a0d1eb-7fde-dff4-225f-92b68fbf7620@linux.intel.com> To: Christoph Hellwig , David Woodhouse , Joerg Roedel , Lu Baolu , Tom Murphy , Tvrtko Ursulin Subject: Re: [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api From: Joonas Lahtinen Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Message-ID: <160439750572.8460.14782978404889004150@jlahtine-mobl.ger.corp.intel.com> User-Agent: alot/0.8.1 Date: Tue, 03 Nov 2020 11:58:26 +0200 Cc: Intel-gfx@lists.freedesktop.org, Ashok Raj , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: iommu-bounces@lists.linux-foundation.org Sender: "iommu" Quoting Tvrtko Ursulin (2020-11-03 11:14:32) > > > On 03/11/2020 02:53, Lu Baolu wrote: > > On 11/2/20 7:52 PM, Tvrtko Ursulin wrote: > >> > >> On 02/11/2020 02:00, Lu Baolu wrote: > >>> Hi Tvrtko, > >>> On 10/12/20 4:44 PM, Tvrtko Ursulin wrote: > >>>> > >>>> On 29/09/2020 01:11, Lu Baolu wrote: > >>>> FYI we have merged the required i915 patches to out tree last week > >>>> or so. I *think* this means they will go into 5.11. So the i915 > >>>> specific workaround patch will not be needed in Intel IOMMU. > >>> > >>> Do you mind telling me what's the status of this fix patch? I tried this > >>> series on v5.10-rc1 with the graphic quirk patch dropped. I am still > >>> seeing dma faults from graphic device. > >> > >> Hmm back then I thought i915 fixes for this would land in 5.11 so I > >> will stick with that. :) (See my quoted text a paragraph above yours.) > > > > What size are those fixes? I am considering pushing this series for > > v5.11. Is it possible to get some acks for those patches and let them > > go to Linus through iommu tree? > > For 5.10 you mean? They feel a bit too large for comfort to go via a > non-i915/drm tree. These are the two patches required: > > https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-gt-next&id=8a473dbadccfc6206150de3db3223c40785da348 > https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-gt-next&id=934941ed5a3070a7833c688c9b1d71484fc01a68 > > I'll copy Joonas as our maintainer - how does the idea of taking the > above two patches through the iommu tree sound to you? Hi Lu, The patches have already been merged into our tree and are heading towards 5.11, so I don't think we should merge them elsewhere. DRM subsystem had the feature freeze for 5.10 at the time of 5.9-rc5 and only drm-intel-fixes pull requests are sent after that. The patches seem to target to eliminate need for a previously used workaround. To me it seems more appropriate for the patches to follow the regular process as new feature for 5.11 to make sure the changes get validated as part of linux-next. Would that work for you? We intend to send the feature pull requests to DRM for 5.11 in the upcoming weeks. Regards, Joonas _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu