From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A1BDB330D34 for ; Fri, 22 May 2026 06:02:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.15 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779429758; cv=none; b=PHOxVqjvz7jNjpv2q/IbvqXJcalk+XcMPfOazI4sBZrC4hXxxytXXayGZpIPBLURcxCP/ozQ7ppXqOdCzeNrIZkx17rLGvWBUChv6vXc+7XFHgEKf8r19XSZmrw+0mDvjbJZj/1J9/CciZCGOcRkOGtn9WUqO5pbUmr5fwLWHBI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779429758; c=relaxed/simple; bh=eb36L2P3NvmDfTQzCsl+4iB764ZICmy72QmzXxmhS1Y=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=JPWFuryfMrm+Fsn2oBdnra8OSCoR8UrLqNLG/kdj77RNCcDDJ+TSlASvWgzg9FQBKKNiBy7sc9xLdqo2B6iixWy1TLC1k+BG/WmIXUIgZPeW866osp984GhVmdJzTzLJYKvTnPMJMMxlLPZqahFBN3xprGSkr27j0pwxWjeRJ/o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=CfA056Er; arc=none smtp.client-ip=198.175.65.15 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="CfA056Er" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1779429757; x=1810965757; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=eb36L2P3NvmDfTQzCsl+4iB764ZICmy72QmzXxmhS1Y=; b=CfA056ErFs49fX59sFfQGSYJDoYHMdDxoNQJQojeIt0b7rzTVC7h4sef h4QmD8McOURrN5On0tO9qxzY8XHrm6qqbsCz/0mP2FNT4oHR2wijVMRxP +ZO92h8BxWCxoF8sIh1//9S9lOGwjjhJB5ki0sWerALTbubzh/n+pxoUG lC9fOyHgV8LzNTVfxngG2/nnMNs/S35cGg/9dfPZq7W6hGZQnZeo+hy+t +6UpJpuhGw/McfL5tY3t/2bJMY40MAO88kGQNedPG1qU/+9gdy6q8/9wn iymLWKXG3ECLYAL1lAw8z2K7lkdxrfweGoUOkX3p+ZOxnw6b4c92IU5Ca g==; X-CSE-ConnectionGUID: BPzpoEK3RYO8tNOZXyn1cA== X-CSE-MsgGUID: DFv5jK4HRaOhoc0ZqT6JWw== X-IronPort-AV: E=McAfee;i="6800,10657,11793"; a="83973370" X-IronPort-AV: E=Sophos;i="6.24,161,1774335600"; d="scan'208";a="83973370" Received: from fmviesa007.fm.intel.com ([10.60.135.147]) by orvoesa107.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 May 2026 23:02:37 -0700 X-CSE-ConnectionGUID: g+Yj186WTEa9Moi1qkaE/g== X-CSE-MsgGUID: xoSQbUtsTmC58tA0TewFgA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.24,161,1774335600"; d="scan'208";a="237775298" Received: from allen-sbox.sh.intel.com (HELO [10.239.159.30]) ([10.239.159.30]) by fmviesa007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 May 2026 23:02:33 -0700 Message-ID: Date: Fri, 22 May 2026 14:01:59 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v6 3/7] iommufd: Allow binding to a noiommu device To: Jacob Pan , linux-kernel@vger.kernel.org, "iommu@lists.linux.dev" , Jason Gunthorpe , Alex Williamson , Joerg Roedel , Mostafa Saleh , David Matlack , Robin Murphy , Nicolin Chen , "Tian, Kevin" , Yi Liu Cc: Saurabh Sengar , skhawaja@google.com, pasha.tatashin@soleen.com, Will Deacon References: <20260521221155.1375144-1-jacob.pan@linux.microsoft.com> <20260521221155.1375144-4-jacob.pan@linux.microsoft.com> Content-Language: en-US From: Baolu Lu In-Reply-To: <20260521221155.1375144-4-jacob.pan@linux.microsoft.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 5/22/26 06:11, Jacob Pan wrote: > From: Jason Gunthorpe > > Allow iommufd to bind devices without an IOMMU (noiommu mode) by creating > a dummy IOMMU group for such devices and skipping hwpt operations. > > This enables noiommu devices to operate through the same iommufd API as IOMMU- > capable devices. > > Reviewed-by: Yi Liu > Signed-off-by: Jason Gunthorpe > Signed-off-by: Jacob Pan Reviewed-by: Lu Baolu