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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 11AA1C64E7B for ; Tue, 13 Oct 2020 02:42:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CFBCA221FC for ; Tue, 13 Oct 2020 02:42:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727877AbgJMAj2 (ORCPT ); Mon, 12 Oct 2020 20:39:28 -0400 Received: from mga11.intel.com ([192.55.52.93]:37649 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727403AbgJMAj1 (ORCPT ); Mon, 12 Oct 2020 20:39:27 -0400 IronPort-SDR: d7BoYj5wM0vxdhHNtuOXTzJXo1wBzGN+Ta5S52RudAT0aILnKJ2Y17D5Pd/nmrBHxPyJWsgeiQ A9eQgV9yIPIQ== X-IronPort-AV: E=McAfee;i="6000,8403,9772"; a="162358894" X-IronPort-AV: E=Sophos;i="5.77,368,1596524400"; d="scan'208";a="162358894" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Oct 2020 17:39:26 -0700 IronPort-SDR: y5z+hZ5cSYkx8JvU5SikKp8uKnzwJcOTZpQUxSZ2OpbG2uHta4q8jOnZrxRAVQIeMo6nhBc5zd USpox1hI//bQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,368,1596524400"; d="scan'208";a="345083735" Received: from allen-box.sh.intel.com (HELO [10.239.159.139]) ([10.239.159.139]) by fmsmga004.fm.intel.com with ESMTP; 12 Oct 2020 17:39:24 -0700 Cc: baolu.lu@linux.intel.com, Ashok Raj , Intel-gfx@lists.freedesktop.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api To: Tvrtko Ursulin , Joerg Roedel , Tom Murphy , David Woodhouse , Christoph Hellwig References: <20200927063437.13988-1-baolu.lu@linux.intel.com> <8bac9e91-36a0-c1d6-a887-4d60567ac75a@linux.intel.com> From: Lu Baolu Message-ID: Date: Tue, 13 Oct 2020 08:32:57 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <8bac9e91-36a0-c1d6-a887-4d60567ac75a@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tvrtko, On 10/12/20 4:44 PM, Tvrtko Ursulin wrote: > > On 29/09/2020 01:11, Lu Baolu wrote: >> Hi Tvrtko, >> >> On 9/28/20 5:44 PM, Tvrtko Ursulin wrote: >>> >>> On 27/09/2020 07:34, Lu Baolu wrote: >>>> Hi, >>>> >>>> The previous post of this series could be found here. >>>> >>>> https://lore.kernel.org/linux-iommu/20200912032200.11489-1-baolu.lu@linux.intel.com/ >>>> >>>> >>>> This version introduce a new patch [4/7] to fix an issue reported here. >>>> >>>> https://lore.kernel.org/linux-iommu/51a1baec-48d1-c0ac-181b-1fba92aa428d@linux.intel.com/ >>>> >>>> >>>> There aren't any other changes. >>>> >>>> Please help to test and review. >>>> >>>> Best regards, >>>> baolu >>>> >>>> Lu Baolu (3): >>>>    iommu: Add quirk for Intel graphic devices in map_sg >>> >>> Since I do have patches to fix i915 to handle this, do we want to >>> co-ordinate the two and avoid having to add this quirk and then later >>> remove it? Or you want to go the staged approach? >> >> I have no preference. It depends on which patch goes first. Let the >> maintainers help here. > > 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. Thanks for letting us know this. I will drop the workaround patch and test the whole series after the next rc1. Best regards, baolu