From patchwork Thu Aug 3 14:31:40 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yi Liu X-Patchwork-Id: 13088 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:9f41:0:b0:3e4:2afc:c1 with SMTP id v1csp1247774vqx; Thu, 3 Aug 2023 09:04:10 -0700 (PDT) X-Google-Smtp-Source: APBJJlGW19lFj9sYfTdvQSYa2WewaON1Waev+Ui90kUMJSO7jZa4oDFR1cZnDzJtJiT0VDUsSFul X-Received: by 2002:a05:6402:31f3:b0:522:3a89:a7bc with SMTP id dy19-20020a05640231f300b005223a89a7bcmr6842718edb.42.1691078649877; Thu, 03 Aug 2023 09:04:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691078649; cv=none; d=google.com; s=arc-20160816; b=aBE8Dpgex+fniGD9646exImwkuQtyOHSdejR9kA2cCu1Am8USW90l8t/pB3drjChFe V2Hh+9AkAz15M+U1FC3lmHu9m39+v8KeG6190vYuMA5eV3n34GuQhcWUL6wWt5Fl2I50 Q+gDtevSaU8vbgqxN6jQS3c/NEdZREHcdUuTG0r6h98perZYHbEbi8LPUiMj6LfjLVlZ WNgUDGmGNwQmy/t4hsOPM6z0DZXT53lFQBdYvTkNr9sneWhCwEe5jxTugYRaIvZur09U PS4OdLlCxEVzRWXVMW76bAdiqpaqNpy7zIdIvYu3qYfzKno1YeB0SmlhJxvXpJJ0ga+g SRaA== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=tP+lX8ozfctbMuVe1ZJxIq0p65sEo2ymZdj+I2FsywM=; fh=25kVo4cotgMzE250R6E3K5ES7E7C2JawiavlW0h5mKU=; b=fZMM0/EnO4Odf0eBlRuzsloCkkXRTeNIsx7zTSH+sJJkRVCyfYMutc5y7mkUePY8Vy My5sxDbbsXhwk8iny6lhbU+RpmpI6wq7CcqaY9h52NwgIRw5uEuTpVPwnHStfiNA5CM9 Gc1TaJrJ3Pceft7vwMIpVmFH/Glor4dh6qOiC6QNdpEmxDfXMZFm/9TVlSQzFgfxn7HZ RCq4m8JkHZW1oVVVC0AORkuC/Xf+l2JuANdjowVkzMRikbDkR0KOYlMNMMwPFTm5I4SV +RtVcphytTam+t3AiuNXZ5Q+EoBBlKnU8ZeMG0GDE6+60aupdNmQg9DrqaRaD0xO3UBr FVsA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=jcNrFXIc; 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 u1-20020a05640207c100b005221f7b8a51si2305789edy.446.2023.08.03.09.03.33; Thu, 03 Aug 2023 09:04:09 -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=jcNrFXIc; 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 S233941AbjHCOhn (ORCPT + 99 others); Thu, 3 Aug 2023 10:37:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45462 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235381AbjHCOhU (ORCPT ); Thu, 3 Aug 2023 10:37:20 -0400 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E81BA5256; Thu, 3 Aug 2023 07:36:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1691073383; x=1722609383; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=5XOAANYi6PhPbrJ+klTCobbNvd+SaqKSvWlM8mBjHuA=; b=jcNrFXIcGGPbGs/XZ/Wthsm8DY8KT7w5UAgREcZGaY6f8505HMNxjrbd nnYN/jsm1wtGnBAIlSIt9D0F7nEtLNMrFUv0CXQcyj8IP9S5G8XoADo9V 47bRzyowJMyyT0op6/sBRFgY45tOGvy6lkeCGpiuUzywjSRQDclaPm13C +qbt9I+Uu7vJfQK0Bu7HByrEM3X6XYksleKQS3cR/kGOAO/XSfDP96e1T t/0ZQ1zM+kQu9p6Ro8RKielCNUnC0MrqdvqUlrnYSz823X9WMHsetYchS hZR7BEmIcnldVi5Rv97gssk0UVZOKMJLdSHqjE6wYobtaX+gF+JiRJG/4 Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10791"; a="372643344" X-IronPort-AV: E=Sophos;i="6.01,252,1684825200"; d="scan'208";a="372643344" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Aug 2023 07:31:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10791"; a="759153147" X-IronPort-AV: E=Sophos;i="6.01,252,1684825200"; d="scan'208";a="759153147" Received: from 984fee00a4c6.jf.intel.com ([10.165.58.231]) by orsmga008.jf.intel.com with ESMTP; 03 Aug 2023 07:31:45 -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 v5 0/4] iommufd: Add iommu hardware info reporting Date: Thu, 3 Aug 2023 07:31:40 -0700 Message-Id: <20230803143144.200945-1-yi.l.liu@intel.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE 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: 1773224486591930927 X-GMAIL-MSGID: 1773224486591930927 iommufd gives userspace the capability to manipulate iommu subsytem. e.g. DMA map/unmap etc. In the near future, it will support iommu nested translation. Different platform vendors have different implementation for the nested translation. For example, Intel VT-d supports using guest I/O page table as the stage-1 translation table. This requires guest I/O page table be compatible with hardware IOMMU. So before set up nested translation, userspace needs to know the hardware iommu information to understand the nested translation requirements. This series reports the iommu hardware information for a given device which has been bound to iommufd. It is preparation work for userspace to allocate hwpt for given device. Like the nested translation support[1]. This series introduces an iommu op to report the iommu hardware info, and an ioctl IOMMU_GET_HW_INFO is added to report such hardware info to user. enum iommu_hw_info_type is defined to differentiate the iommu hardware info reported to user hence user can decode them. This series only adds the framework for iommu hw info reporting, the complete reporting path needs vendor specific definition and driver support. The full code is available in [1] as well. [1] https://github.com/yiliu1765/iommufd/tree/wip/iommufd_nesting_08032023-yi (only the hw_info report path is the latest, other parts is wip) Change log: v5: - Return hw_info_type in the .hw_info op, hence drop hw_info_type field in iommu_ops (Kevin) - Add Jason's r-b for patch 01 - Address coding style comments from Jason and Kevin w.r.t. patch 02, 03 and 04 v4: https://lore.kernel.org/linux-iommu/20230724105936.107042-1-yi.l.liu@intel.com/ - Rename ioctl to IOMMU_GET_HW_INFO and structure to iommu_hw_info - Move the iommufd_get_hw_info handler to main.c - Place iommu_hw_info prior to iommu_hwpt_alloc - Update the function namings accordingly - Update uapi kdocs v3: https://lore.kernel.org/linux-iommu/20230511143024.19542-1-yi.l.liu@intel.com/#t - Add r-b from Baolu - Rename IOMMU_HW_INFO_TYPE_DEFAULT to be IOMMU_HW_INFO_TYPE_NONE to better suit what it means - Let IOMMU_DEVICE_GET_HW_INFO succeed even the underlying iommu driver does not have driver-specific data to report per below remark. https://lore.kernel.org/kvm/ZAcwJSK%2F9UVI9LXu@nvidia.com/ v2: https://lore.kernel.org/linux-iommu/20230309075358.571567-1-yi.l.liu@intel.com/ - Drop patch 05 of v1 as it is already covered by other series - Rename the capability info to be iommu hardware info v1: https://lore.kernel.org/linux-iommu/20230209041642.9346-1-yi.l.liu@intel.com/ Regards, Yi Liu Lu Baolu (1): iommu: Add new iommu op to get iommu hardware information Nicolin Chen (1): iommufd/selftest: Add coverage for IOMMU_GET_HW_INFO ioctl Yi Liu (2): iommu: Move dev_iommu_ops() to private header iommufd: Add IOMMU_GET_HW_INFO drivers/iommu/iommu-priv.h | 11 +++ drivers/iommu/iommufd/iommufd_test.h | 9 +++ drivers/iommu/iommufd/main.c | 79 +++++++++++++++++++ drivers/iommu/iommufd/selftest.c | 16 ++++ include/linux/iommu.h | 20 +++-- include/uapi/linux/iommufd.h | 44 +++++++++++ tools/testing/selftests/iommu/iommufd.c | 17 +++- tools/testing/selftests/iommu/iommufd_utils.h | 26 ++++++ 8 files changed, 210 insertions(+), 12 deletions(-)