From patchwork Tue Aug 8 15:35:08 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yi Liu X-Patchwork-Id: 132660 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:c44e:0:b0:3f2:4152:657d with SMTP id w14csp2298167vqr; Tue, 8 Aug 2023 11:01:43 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGTW+GVwFYfC9D10ylzeMzYVij8bLQvF3pEDwPC+ij1nbgbZXLVIiBE5xgNtDCm98yqgHC5 X-Received: by 2002:a17:90a:8989:b0:256:8dbd:74fa with SMTP id v9-20020a17090a898900b002568dbd74famr280858pjn.22.1691517702888; Tue, 08 Aug 2023 11:01:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691517702; cv=none; d=google.com; s=arc-20160816; b=SK3l/FetumxNPCxobbLLrQcCio8AXtDRz8gDJ6dtFGc3pRG/F/lHHplGL/pub23I6B O2+Fk/YMLXZT6HPJM3GCMlVSyiJKBo7S35ngWr8wcgosZXRD9fyNYAroSUyFmKMZB3/y EjzHnS6TH5MZ7XzMCfT/9ZCAImKmIQa7qvkpN8SdrFMR0Sa5vBhZxt7hGqWyvPK6hFFq A68Hz+Mbr/EHfItv67CvAuIzaCJerCmhaqkxRsvaE79sIDStaryI6x1bzcykKES/t/A4 OIasVYP2PRMxum58gyvtc4XoKLlJ7TKBbezNVBdX2rAkDfhqlMgPrrxcCgLHo1EWimXY h/3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=mNzVbIS9esikMQCX6OsBAZkjdkau0ltmXr1Ruc5Qz5o=; fh=25kVo4cotgMzE250R6E3K5ES7E7C2JawiavlW0h5mKU=; b=G3E/1oO7TQcAara6ywyjlB5xrQF+sAZiHjcKJbf6aoli7445teGCBuT3SZPHZquU1M y8rFElFsVKxv+Qxwb4Rabw6fzoh2ySsSDIVf1dbIoXoN2WocHNh+dsNCk4qecCw0KqcZ d5+JIeXJ8sYZHjdV11ltAjbzSArSJcHAtBKmgGr8k7uTU3/8x0jKm7GNPANYsvV1QrH5 OVZtM3eYF56HnUegcUFuo+9SN6OvwfUUKVibGXT+eNazxwJ5BCyD6lkFU9gwBDUiIXE8 SsxtGn2hRSE13InXl3Awjn+vk1CkNUw9/9XJGmtfeewyPn6Tbg6GNNyx68mcKwLN5VuJ I86Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=lcmjl4wh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z4-20020a170903018400b001b9c992945fsi7987272plg.555.2023.08.08.11.01.28; Tue, 08 Aug 2023 11:01:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=lcmjl4wh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229527AbjHHREg (ORCPT + 99 others); Tue, 8 Aug 2023 13:04:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232190AbjHHRDu (ORCPT ); Tue, 8 Aug 2023 13:03:50 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0D4C219BDE; Tue, 8 Aug 2023 09:01:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1691510504; x=1723046504; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=sxfubDWI2gwfOBW2/jdEN8IlvwFA21yaOXGd5zVExW0=; b=lcmjl4whkksy6IFNqKx/esLaIMPkA32cizyxlGGfjhB3a8j/hPNyisWX J3AMswxSRFDpAOTVsQ4UPLBnt0DdghROT/iAuWmgOGKQO+ra/qNnJmO3m DEnivy/on7oalB3CiEp+kmDL5vSBDkkDr9rPwrjnqHKavYKdeGWCz5Ku+ 23EyRCYi2pke2yfXm0PS0+8I2E9jhvQ9v7bwdf/qSbGCLx6Iw5J/pJHWI eC3pYSReE2owJ+Pcpcqase06jyJTMO4T+KdTY23lN5Hu6kncdUqMFOJoJ NnYg5YkfBSVI/G8lmsY8DyyBMbqO19mBt9S9QJznqu6pJR1q8NgrKQEKW A==; X-IronPort-AV: E=McAfee;i="6600,9927,10795"; a="350449299" X-IronPort-AV: E=Sophos;i="6.01,156,1684825200"; d="scan'208";a="350449299" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Aug 2023 08:35:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10795"; a="855126974" X-IronPort-AV: E=Sophos;i="6.01,156,1684825200"; d="scan'208";a="855126974" Received: from 984fee00a4c6.jf.intel.com ([10.165.58.231]) by orsmga004.jf.intel.com with ESMTP; 08 Aug 2023 08:35:13 -0700 From: Yi Liu To: joro@8bytes.org, alex.williamson@redhat.com, jgg@nvidia.com, kevin.tian@intel.com, robin.murphy@arm.com, baolu.lu@linux.intel.com Cc: cohuck@redhat.com, eric.auger@redhat.com, nicolinc@nvidia.com, kvm@vger.kernel.org, mjrosato@linux.ibm.com, chao.p.peng@linux.intel.com, yi.l.liu@intel.com, yi.y.sun@linux.intel.com, peterx@redhat.com, jasowang@redhat.com, shameerali.kolothum.thodi@huawei.com, lulu@redhat.com, suravee.suthikulpanit@amd.com, iommu@lists.linux.dev, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, zhenzhong.duan@intel.com Subject: [PATCH v6 2/4] iommu: Add new iommu op to get iommu hardware information Date: Tue, 8 Aug 2023 08:35:08 -0700 Message-Id: <20230808153510.4170-3-yi.l.liu@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230808153510.4170-1-yi.l.liu@intel.com> References: <20230808153510.4170-1-yi.l.liu@intel.com> MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1773684867011870914 X-GMAIL-MSGID: 1773684867011870914 From: Lu Baolu Introduce a new iommu op to get the IOMMU hardware capabilities for iommufd. This information will be used by any vIOMMU driver which is owned by userspace. This op chooses to make the special parameters opaque to the core. This suits the current usage model where accessing any of the IOMMU device special parameters does require a userspace driver that matches the kernel driver. If a need for common parameters, implemented similarly by several drivers, arises then there's room in the design to grow a generic parameter set as well. No wrapper API is added as it is supposed to be used by iommufd only. Different IOMMU hardware would have different hardware information. So the information reported differs as well. To let the external user understand the difference. enum iommu_hw_info_type is defined. For the iommu drivers that are capable to report hardware information, it should have a unique iommu_hw_info_type and return to caller. For the driver doesn't report hardware information, caller just uses IOMMU_HW_INFO_TYPE_NONE if a type is required. Signed-off-by: Lu Baolu Co-developed-by: Nicolin Chen Signed-off-by: Nicolin Chen Signed-off-by: Yi Liu --- include/linux/iommu.h | 9 +++++++++ include/uapi/linux/iommufd.h | 9 +++++++++ 2 files changed, 18 insertions(+) diff --git a/include/linux/iommu.h b/include/linux/iommu.h index e0245aa82b75..f2d6a3989713 100644 --- a/include/linux/iommu.h +++ b/include/linux/iommu.h @@ -228,6 +228,14 @@ struct iommu_iotlb_gather { /** * struct iommu_ops - iommu ops and capabilities * @capable: check capability + * @hw_info: IOMMU hardware information. The type of the returned data is + * marked by the output type of this op. Type is one of + * enum iommu_hw_info_type defined in include/uapi/linux/iommufd.h. + * The drivers that support this op should define a unique type + * in include/uapi/linux/iommufd.h. The data buffer returned by this + * op is allocated in the IOMMU driver and the caller should free it + * after use. Return the data buffer if success, or ERR_PTR on + * failure. * @domain_alloc: allocate iommu domain * @probe_device: Add device to iommu driver handling * @release_device: Remove device from iommu driver handling @@ -257,6 +265,7 @@ struct iommu_iotlb_gather { */ struct iommu_ops { bool (*capable)(struct device *dev, enum iommu_cap); + void *(*hw_info)(struct device *dev, u32 *length, u32 *type); /* Domain allocation and freeing by the iommu driver */ struct iommu_domain *(*domain_alloc)(unsigned iommu_domain_type); diff --git a/include/uapi/linux/iommufd.h b/include/uapi/linux/iommufd.h index 8245c01adca6..ac11ace21edb 100644 --- a/include/uapi/linux/iommufd.h +++ b/include/uapi/linux/iommufd.h @@ -370,4 +370,13 @@ struct iommu_hwpt_alloc { __u32 __reserved; }; #define IOMMU_HWPT_ALLOC _IO(IOMMUFD_TYPE, IOMMUFD_CMD_HWPT_ALLOC) + +/** + * enum iommu_hw_info_type - IOMMU Hardware Info Types + * @IOMMU_HW_INFO_TYPE_NONE: Used by the drivers that do not report hardware + * info + */ +enum iommu_hw_info_type { + IOMMU_HW_INFO_TYPE_NONE, +}; #endif