From patchwork Fri Feb 3 08:33:44 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yi Liu X-Patchwork-Id: 13127177 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 9C64DC61DA4 for ; Fri, 3 Feb 2023 08:33:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232359AbjBCIdz (ORCPT ); Fri, 3 Feb 2023 03:33:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232363AbjBCIdw (ORCPT ); Fri, 3 Feb 2023 03:33:52 -0500 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A46B66F8A for ; Fri, 3 Feb 2023 00:33:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675413229; x=1706949229; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=rmXRKWy5ZFKKndQf1wsA8tFOL8az3jnsBzxF82eYX7I=; b=Uh2GHAhCsac4oXv64JHwhaRUyNRskvvcLorgpNmDJAxxVF5D3Pklha52 EzZe2H9X7mRp03jw4mF563mh8cmlNtiVETEsTjJ4Nozyi+0yliZMAEnvE wJvgBN5BqAqepUqJcWGKjKQkAgeKvSG3MoUdpSD8h6DoBd64q8FK4HjOG gLlBvRQCYElInq7mOWUekNNutr/3EzOxl7ou2wJb7GeCHhu3A93ql/fDF LzY2W+qcgt+G/FKHX3KVFLfiAfSbJi4f/B5Z7dLGsc1LmpmHCwpd8ug5D yY7IF/02pI2zqrinm6CuWWBmoJUh49A4UHOa0Zqhzik8DkwTbSkwbXzRn g==; X-IronPort-AV: E=McAfee;i="6500,9779,10609"; a="391089873" X-IronPort-AV: E=Sophos;i="5.97,269,1669104000"; d="scan'208";a="391089873" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2023 00:33:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10609"; a="667581569" X-IronPort-AV: E=Sophos;i="5.97,269,1669104000"; d="scan'208";a="667581569" Received: from 984fee00a4c6.jf.intel.com ([10.165.58.231]) by fmsmga007.fm.intel.com with ESMTP; 03 Feb 2023 00:33:47 -0800 From: Yi Liu To: alex.williamson@redhat.com, jgg@nvidia.com Cc: kevin.tian@intel.com, chao.p.peng@linux.intel.com, eric.auger@redhat.com, yi.l.liu@intel.com, yi.y.sun@linux.intel.com, kvm@vger.kernel.org Subject: [PATCH v2 1/2] vfio: Update the kdoc for vfio_device_ops Date: Fri, 3 Feb 2023 00:33:44 -0800 Message-Id: <20230203083345.711443-2-yi.l.liu@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230203083345.711443-1-yi.l.liu@intel.com> References: <20230203083345.711443-1-yi.l.liu@intel.com> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org this is missed when adding bind_iommufd/unbind_iommufd and attach_ioas. Signed-off-by: Yi Liu Reviewed-by: Kevin Tian --- include/linux/vfio.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/include/linux/vfio.h b/include/linux/vfio.h index 35be78e9ae57..cc7685386b53 100644 --- a/include/linux/vfio.h +++ b/include/linux/vfio.h @@ -70,6 +70,10 @@ struct vfio_device { * * @init: initialize private fields in device structure * @release: Reclaim private fields in device structure + * @bind_iommufd: Called when binding the device to an iommufd + * @unbind_iommufd: Opposite of bind_iommufd + * @attach_ioas: Called when attaching device to an IOAS/HWPT managed by the + * bound iommufd. Undo in unbind_iommufd. * @open_device: Called when the first file descriptor is opened for this device * @close_device: Opposite of open_device * @read: Perform read(2) on device file descriptor From patchwork Fri Feb 3 08:33:45 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yi Liu X-Patchwork-Id: 13127178 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 3206CC6379F for ; Fri, 3 Feb 2023 08:33:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232374AbjBCId5 (ORCPT ); Fri, 3 Feb 2023 03:33:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41634 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232377AbjBCIdz (ORCPT ); Fri, 3 Feb 2023 03:33:55 -0500 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D6B570D75 for ; Fri, 3 Feb 2023 00:33:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675413232; x=1706949232; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=r+vy3TMDiXv0Bz+nfF+mbx1EGQbhvpt5NoZHh1YSg6A=; b=h16uxYkiY4lys1nDWgQT2ZRnquzA06FC/XDxpLu0HdEd9TSbHMAtyHQj CZG3TZ1tWMNDWRcduN+XAEAczIKwp79ux+D43mLnInvAYsMCB1HS4AgXo Z8T+g80+3UUsVpjS5mYepHUFxLIoBjFNjQQ/muFWo2kcaj0k10TSS8Zix 4IgnFRujSYg/4STZVu4zIgL1TaxAid1d3hCsSSXNDzXTFOV89hdWZyBCL YIYaIQm1fcN8YUii3UnR7UjeK+tEKClhH4EB1c4aFC0F3E4CMVCL94sbc HjD1gUVRaECR6d/IFcFrxnpUBfafEUB2d21ci6ZpA9vL1R9uzQT9APEZ5 Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10609"; a="391089880" X-IronPort-AV: E=Sophos;i="5.97,269,1669104000"; d="scan'208";a="391089880" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2023 00:33:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10609"; a="667581575" X-IronPort-AV: E=Sophos;i="5.97,269,1669104000"; d="scan'208";a="667581575" Received: from 984fee00a4c6.jf.intel.com ([10.165.58.231]) by fmsmga007.fm.intel.com with ESMTP; 03 Feb 2023 00:33:48 -0800 From: Yi Liu To: alex.williamson@redhat.com, jgg@nvidia.com Cc: kevin.tian@intel.com, chao.p.peng@linux.intel.com, eric.auger@redhat.com, yi.l.liu@intel.com, yi.y.sun@linux.intel.com, kvm@vger.kernel.org Subject: [PATCH v2 2/2] docs: vfio: Update vfio.rst per latest interfaces Date: Fri, 3 Feb 2023 00:33:45 -0800 Message-Id: <20230203083345.711443-3-yi.l.liu@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230203083345.711443-1-yi.l.liu@intel.com> References: <20230203083345.711443-1-yi.l.liu@intel.com> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org this imports the latest vfio_device_ops definition to vfio.rst. Signed-off-by: Yi Liu Signed-off-by: Yi Liu --- Documentation/driver-api/vfio.rst | 70 +++++++++++++++++++++---------- 1 file changed, 47 insertions(+), 23 deletions(-) diff --git a/Documentation/driver-api/vfio.rst b/Documentation/driver-api/vfio.rst index c663b6f97825..f38ab4ae1244 100644 --- a/Documentation/driver-api/vfio.rst +++ b/Documentation/driver-api/vfio.rst @@ -249,19 +249,21 @@ VFIO bus driver API VFIO bus drivers, such as vfio-pci make use of only a few interfaces into VFIO core. When devices are bound and unbound to the driver, -the driver should call vfio_register_group_dev() and -vfio_unregister_group_dev() respectively:: +Following interfaces are called when devices are bound to and +unbound from the driver:: - void vfio_init_group_dev(struct vfio_device *device, - struct device *dev, - const struct vfio_device_ops *ops); - void vfio_uninit_group_dev(struct vfio_device *device); int vfio_register_group_dev(struct vfio_device *device); + int vfio_register_emulated_iommu_dev(struct vfio_device *device); void vfio_unregister_group_dev(struct vfio_device *device); The driver should embed the vfio_device in its own structure and call -vfio_init_group_dev() to pre-configure it before going to registration -and call vfio_uninit_group_dev() after completing the un-registration. +vfio_alloc_device() to allocate the structure, and can register +@init/@release callbacks to manage any private state wrapping the +vfio_device. + + vfio_alloc_device(dev_struct, member, dev, ops); + void vfio_put_device(struct vfio_device *device); + vfio_register_group_dev() indicates to the core to begin tracking the iommu_group of the specified dev and register the dev as owned by a VFIO bus driver. Once vfio_register_group_dev() returns it is possible for userspace to @@ -270,28 +272,50 @@ ready before calling it. The driver provides an ops structure for callbacks similar to a file operations structure:: struct vfio_device_ops { - int (*open)(struct vfio_device *vdev); + char *name; + int (*init)(struct vfio_device *vdev); void (*release)(struct vfio_device *vdev); + int (*bind_iommufd)(struct vfio_device *vdev, + struct iommufd_ctx *ictx, u32 *out_device_id); + void (*unbind_iommufd)(struct vfio_device *vdev); + int (*attach_ioas)(struct vfio_device *vdev, u32 *pt_id); + int (*open_device)(struct vfio_device *vdev); + void (*close_device)(struct vfio_device *vdev); ssize_t (*read)(struct vfio_device *vdev, char __user *buf, size_t count, loff_t *ppos); - ssize_t (*write)(struct vfio_device *vdev, - const char __user *buf, - size_t size, loff_t *ppos); + ssize_t (*write)(struct vfio_device *vdev, const char __user *buf, + size_t count, loff_t *size); long (*ioctl)(struct vfio_device *vdev, unsigned int cmd, unsigned long arg); - int (*mmap)(struct vfio_device *vdev, - struct vm_area_struct *vma); - }; + int (*mmap)(struct vfio_device *vdev, struct vm_area_struct *vma); + void (*request)(struct vfio_device *vdev, unsigned int count); + int (*match)(struct vfio_device *vdev, char *buf); + void (*dma_unmap)(struct vfio_device *vdev, u64 iova, u64 length); + int (*device_feature)(struct vfio_device *device, u32 flags, + void __user *arg, size_t argsz); +}; Each function is passed the vdev that was originally registered -in the vfio_register_group_dev() call above. This allows the bus driver -to obtain its private data using container_of(). The open/release -callbacks are issued when a new file descriptor is created for a -device (via VFIO_GROUP_GET_DEVICE_FD). The ioctl interface provides -a direct pass through for VFIO_DEVICE_* ioctls. The read/write/mmap -interfaces implement the device region access defined by the device's -own VFIO_DEVICE_GET_REGION_INFO ioctl. - +in the vfio_register_group_dev() or vfio_register_emulated_iommu_dev() +call above. This allows the bus driver to obtain its private data using +container_of(). +- The init/release callbacks are issued when vfio_device is initialized +- and released. +- The open/close_device callbacks are issued when a new file descriptor is + created for a device (via VFIO_GROUP_GET_DEVICE_FD). +- The ioctl interface provides a direct pass through for VFIO_DEVICE_* ioctls. +- The [un]bind_iommufd callbacks are issued when the device is bound to +- and unbound from iommufd. +- The attach_ioas callback is issued when the device is attached to an IOAS + managed by the bound iommufd. The attached IOAS is automatically detached + when the device is unbound from the iommufd. +- The read/write/mmap interfaces implement the device region access defined by + the device's own VFIO_DEVICE_GET_REGION_INFO ioctl. +- The request callback is issued when device is going to be unregistered. +- The dma_unmap callback is issued when a range of iova's are unmapped in + the container or IOAS attached by the device. Drivers which care about + DMA unmap can implement this callback and must tolerate receiving unmap + notifications before the device is opened. PPC64 sPAPR implementation note -------------------------------