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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 05FEAC64EC4 for ; Thu, 9 Mar 2023 01:22:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229582AbjCIBWF (ORCPT ); Wed, 8 Mar 2023 20:22:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58516 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229468AbjCIBWE (ORCPT ); Wed, 8 Mar 2023 20:22:04 -0500 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 49AE3B06E4; Wed, 8 Mar 2023 17:22:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1678324923; x=1709860923; h=message-id:date:mime-version:cc:subject:to:references: from:in-reply-to:content-transfer-encoding; bh=q1aDAPWSfqWw8MzeFLZh49l8q8u0K/Yqd7U27/xelmY=; b=IcHxGlu/SRw73r/DtAOV0UqOFMuhlpSh8b1tr5ear+97pXwuLpVOj9vK CiL7aRQp6+G1HnsvMzBSmviShJlCYYYfJeiAJh8XK3cvZxZMj+CbR6x4d SbKMQaF1EFawJ7Dk10Xo7CeGyt5HTa2CndEdBEnM/TXB2qS/AyLaw5gv6 I473Gp2JXEVM4zG78avMvLTk3bOHEV+gyK79HNXP0ncqnOTBrQmNUUF94 84htsY4/BbA1TYHhtFSFZogNEE/q1RmpPNQCiwM4l6b/llFIQBF3cGrgQ AEE2XHQqPk0wGJiJkpqwKLvoWz5t9/PlKOOIL1fBXR4tVfMoEKE7N1vhe g==; X-IronPort-AV: E=McAfee;i="6500,9779,10643"; a="337850699" X-IronPort-AV: E=Sophos;i="5.98,244,1673942400"; d="scan'208";a="337850699" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Mar 2023 17:22:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10643"; a="851333022" X-IronPort-AV: E=Sophos;i="5.98,244,1673942400"; d="scan'208";a="851333022" Received: from allen-box.sh.intel.com (HELO [10.239.159.48]) ([10.239.159.48]) by orsmga005.jf.intel.com with ESMTP; 08 Mar 2023 17:22:00 -0800 Message-ID: <604a840b-ab12-5cd3-e41a-f481aafeaeed@linux.intel.com> Date: Thu, 9 Mar 2023 09:21:01 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Cc: baolu.lu@linux.intel.com, kvm@vger.kernel.org, Nicolin Chen , Yi Liu Subject: Re: [PATCH v2 15/17] iommufd: Add IOMMU_HWPT_ALLOC Content-Language: en-US To: Jason Gunthorpe , iommu@lists.linux.dev, Kevin Tian , linux-kselftest@vger.kernel.org References: <15-v2-51b9896e7862+8a8c-iommufd_alloc_jgg@nvidia.com> From: Baolu Lu In-Reply-To: <15-v2-51b9896e7862+8a8c-iommufd_alloc_jgg@nvidia.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On 3/8/23 8:35 AM, Jason Gunthorpe wrote: > This allows userspace to manually create HWPTs on IOAS's and then use > those HWPTs as inputs to iommufd_device_attach/replace(). > > Following series will extend this to allow creating iommu_domains with > driver specific parameters. > > Signed-off-by: Jason Gunthorpe Reviewed-by: Lu Baolu Best regards, baolu