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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 52C54C02197 for ; Wed, 5 Feb 2025 03:48:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:To:Subject:Cc:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=MLaFTGCPEcg9NYXwrgf9SMfKqQ9G+0WJl/NqM7xYYn8=; b=ltZxvPeUuIDpY5IaDGnxaMElwG 3UzrfVexbFStXGrjPJCEeF20GJ4FXzfIhc5YPgaC5cSRG8i95bUNKfFF9kP5hRtwvEGTu9SHRSsOP 7Lb7hylTwxy8hJ3TMrZMH1MCWIzqv4wexhQQ9yUqv6kIaoNRqAsFupDNTSJgkhNcTh47dYJSqe4cO 9Sbe08z5qgfMuyqVnvTvULNuqsfCZj4Gdsd1JobxlmrIB3NBMgijY36HYqY8FMTVkI93tgU+MYD5t iJgahyj8BFLQmNDLpJ6oZLtBX4mHLgGz/kOplau15C3waPLRCYYQkDj33gFhoHPFpBwUm70XwgtM1 iFkkEaQQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1tfWOf-00000002FDC-3zfa; Wed, 05 Feb 2025 03:48:17 +0000 Received: from mgamail.intel.com ([198.175.65.19]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1tfWLt-00000002EnA-2SDX for linux-arm-kernel@lists.infradead.org; Wed, 05 Feb 2025 03:45:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1738727126; x=1770263126; h=message-id:date:mime-version:cc:subject:to:references: from:in-reply-to:content-transfer-encoding; bh=MLaFTGCPEcg9NYXwrgf9SMfKqQ9G+0WJl/NqM7xYYn8=; b=VvATrEvhkmDf75fZkASa/BuMQ5S34yH3xxXbcs/j40/+NmfiSfAVjgsf diiw5VwFMo1InONZ1f+4puJ4O96vzaw52JLRK/qxub79d1h3EEcxXFOfp dm1XUpcWWcsIGRc1usonXq8caftrGMi8cDuIGY4wyOgSs9aeSNojSz4Vx 5d+c3f4LB24vHqOdq/XShGYEFUEGC6OqKjUQEdAptcx64ZTHJum+ltG2n 7fxtcuSnVRYgbhl6EQa+ZAMMXBQtm5PyZZcxfZM/Q6mqxKJfCTkf9fFcf 5k1BgtPY8YJ0CkMynP0/XjXBafr3Nhwx/Wz5/OdObp57y2q0mIMZInpgY g==; X-CSE-ConnectionGUID: aje5BTZ7Thi0RRiJ0Gb//Q== X-CSE-MsgGUID: W+CoHGsYQ0mz5clVMldnNQ== X-IronPort-AV: E=McAfee;i="6700,10204,11336"; a="39165407" X-IronPort-AV: E=Sophos;i="6.13,260,1732608000"; d="scan'208";a="39165407" Received: from orviesa002.jf.intel.com ([10.64.159.142]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Feb 2025 19:45:25 -0800 X-CSE-ConnectionGUID: WpR9JSfURxSI/IIjqWagHg== X-CSE-MsgGUID: qbIxOqA5Tj+fNgVN36xa1g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.13,260,1732608000"; d="scan'208";a="141642470" Received: from blu2-mobl.ccr.corp.intel.com (HELO [10.124.242.149]) ([10.124.242.149]) by orviesa002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Feb 2025 19:45:18 -0800 Message-ID: <284dd081-8d53-45ef-ae18-78b0388c98ca@linux.intel.com> Date: Wed, 5 Feb 2025 11:45:15 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: baolu.lu@linux.intel.com, Zhangfei Gao , acpica-devel@lists.linux.dev, iommu@lists.linux.dev, Joerg Roedel , Kevin Tian , kvm@vger.kernel.org, Len Brown , linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Lorenzo Pieralisi , "Rafael J. Wysocki" , Robert Moore , Robin Murphy , Sudeep Holla , Will Deacon , Alex Williamson , Donald Dutile , Eric Auger , Hanjun Guo , Jean-Philippe Brucker , Jerry Snitselaar , Moritz Fischer , Michael Shavit , Nicolin Chen , patches@lists.linux.dev, "Rafael J. Wysocki" , Shameerali Kolothum Thodi , Mostafa Saleh Subject: Re: [PATCH v4 00/12] Initial support for SMMUv3 nested translation To: Jason Gunthorpe References: <0-v4-9e99b76f3518+3a8-smmuv3_nesting_jgg@nvidia.com> <20241112182938.GA172989@nvidia.com> <20241113012359.GB35230@nvidia.com> <9df3dd17-375a-4327-b2a8-e9f7690d81b1@linux.intel.com> <20241113164316.GL35230@nvidia.com> <6ed97a10-853f-429e-8506-94b218050ad3@linux.intel.com> <20241115175522.GA35230@nvidia.com> <20250122192622.GA965540@nvidia.com> Content-Language: en-US From: Baolu Lu In-Reply-To: <20250122192622.GA965540@nvidia.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250204_194525_689911_87E015B1 X-CRM114-Status: GOOD ( 12.10 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2025/1/23 3:26, Jason Gunthorpe wrote: > On Fri, Nov 15, 2024 at 01:55:22PM -0400, Jason Gunthorpe wrote: >>>> I need your help to remove IOMMU_DEV_FEAT_IOPF from the intel >>>> driver. I have a patch series that eliminates it from all the other >>>> drivers, and I wrote a patch to remove FEAT_SVA from intel.. >>> Yes, sure. Let's make this happen in the next cycle. >>> >>> FEAT_IOPF could be removed. IOPF manipulation can be handled in the >>> domain attachment path. A per-device refcount can be implemented. This >>> count increments with each iopf-capable domain attachment and decrements >>> with each detachment. PCI PRI is enabled for the first iopf-capable >>> domain and disabled when the last one is removed. Probably we can also >>> solve the PF/VF sharing PRI issue. >> Here is what I have so far, if you send me a patch for vt-d to move >> FEAT_IOPF into attach as you describe above (see what I did to arm for >> example), then I can send it next cycle >> >> https://github.com/jgunthorpe/linux/commits/iommu_no_feat/ > Hey Baolu, a reminder on this, lets try for it next cycle? Oh, I forgot this. Thanks for the reminding. Sure, let's try to make it in the next cycle. --- baolu