Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp4662710pxu; Tue, 13 Oct 2020 04:16:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw09Kq+bxeyLPmcvPOglVV1CFy9M6GpbbHEc8ymcmBjocBiKDfE0d4ThU/fZKc8eZiWjVKT X-Received: by 2002:a17:906:4b1a:: with SMTP id y26mr21362640eju.350.1602587805778; Tue, 13 Oct 2020 04:16:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602587805; cv=none; d=google.com; s=arc-20160816; b=T3qHlAvMys0vjA9TVvuZrnL1h0LBBEHY21Ar0NyvDLUeiHLj0ZyW/i65UEXhK9HZ7N L08rw6rcDT7ThmU1XuNCLO1OmCstgPsHvF8edMiD/vOvdgbh+U/zrveIYMbn2ujlxrBa sYb/5RUCANiOE/wqYhm3jqllrgDECq0B1wB1fREs/qUYj8v8kJo5RQA6DuPmFgzxDTmV tJA2JitImJA7pmLihO9wepkdj6KzF06IqumufMxkvFL4dWsfzhtiUDrB4+MOZa3X4o1w 8GUczOpCd/kZXx9aVOVpiBLeJH/tGXY4bPIY5LY4OubVSq73JiSoH2dAaKEcgAJlTuCD ejZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :to:subject:cc:ironport-sdr:ironport-sdr; bh=U3p7TuSJZDmvDcfPJKUDLxd88HVHM/8PD+mwnaLCJys=; b=NcKe2xou53hkpop8MBc2UizwuDBH4V6IPZkvQdHCboqkoPasWrvK24NyCpY2Zb1zqr Xf9MKtvWuqjufg8fB80l2cmG/M6ZyV8l7BW5l5SEKcoFePO/pn9PmMJUriNgp2L9jexN F4QNVaUSEcfqsLPce/fo+k16qGzeu1a28NkSiGp1PwnIdmXTKncf2Otrf6jVYXoNgwcU p157HhgMBu/r3vM0CQ5nug8j7s0x9Ct/31kj+f/6/ICYtirL9/YNwy1W/nY3fQeQ9X2L 6Y7RkNCzglHuoeK1AQToqy0FprvDMRhdKRE/+MgRUGxxa+Z+5oGNVeEHeYG+rx/DZPQg vN9A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d5si13858702ejz.709.2020.10.13.04.16.23; Tue, 13 Oct 2020 04:16:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727871AbgJMAj2 (ORCPT + 99 others); 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