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 76292C77B73 for ; Thu, 18 May 2023 20:03:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230116AbjERUDR (ORCPT ); Thu, 18 May 2023 16:03:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229948AbjERUDP (ORCPT ); Thu, 18 May 2023 16:03:15 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 03370E72 for ; Thu, 18 May 2023 13:02:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1684440146; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NxSZSODI2u28vy1MvKpnEmFi7Q8e7Naitxzu3Z7bWS4=; b=L5JLHyNkieNxvecedNC8TpHSgDgEKleBRAHO/dijq6Y+YowMIxYgbiYwtkddlP2yG96V3i /pKyLl1+tBdfjc5tj296MYb4C22XXadG2l2j1+l1RECuSluOTN55M/OscbNHC5II9FNiaq Y+KqkkwOXXA+jZHrOG8Hb/EBouKK0tY= Received: from mail-io1-f72.google.com (mail-io1-f72.google.com [209.85.166.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-350-Xd64Zc6ANt2H8_XcvxfCGg-1; Thu, 18 May 2023 16:02:24 -0400 X-MC-Unique: Xd64Zc6ANt2H8_XcvxfCGg-1 Received: by mail-io1-f72.google.com with SMTP id ca18e2360f4ac-766588051b3so197012039f.2 for ; Thu, 18 May 2023 13:02:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684440144; x=1687032144; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=NxSZSODI2u28vy1MvKpnEmFi7Q8e7Naitxzu3Z7bWS4=; b=Scmcu+hFQK58YOW43+tLEJXz1VQuQFVCl5HBOwpr/ua4WO0jfEFwpX4wCRhgAQwRBb sXKsKHPFpwV/W8iQlXD4k43xg/3HvvAOFtRPW11DrpLtElELyxWMZvQjg/pdrXfCCDk5 4Bf6B7JBQ+e9H7HlFxlCI9IW6wrqAlR3YBS1qtHpr1YEScMhbQMoUBFeL9fXyHTSJlxx 3KEa4zBtutuW6BSqgm9vH9YoPLDQQlI7e1d34BwkmD8InKecntYEVkhvyaAPSxxZhQWy wTQuzm/9m8Iwd/U33mOBTPHFWmwJhMGpz77n40je7TCmgL+uy0yNb2iIqz6s1VYZmVON 6n1w== X-Gm-Message-State: AC+VfDwI7s0ylNgFGKv/IGZ13HAtxJb9BpOiqZB1hijmNhgMk8hafZDz /uU21CrAk+XqghRkrdOpQGMeznkp1k+Yiq0j5dfzf3JVUg8VO+qcfnxBkvcJ5seuhh4d9KFu3Q0 13R/wWCgzskGDvFcRje/olA== X-Received: by 2002:a05:6602:42cc:b0:770:f25:eea with SMTP id ce12-20020a05660242cc00b007700f250eeamr8109526iob.4.1684440143735; Thu, 18 May 2023 13:02:23 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ78r16hyXJua6dwpFFlo7TPCXcK29v0VmS1Dgb685o6EqQWCUg5zZuAs+XNJa9yraJYnBOI3w== X-Received: by 2002:a05:6602:42cc:b0:770:f25:eea with SMTP id ce12-20020a05660242cc00b007700f250eeamr8109505iob.4.1684440143240; Thu, 18 May 2023 13:02:23 -0700 (PDT) Received: from redhat.com ([38.15.36.239]) by smtp.gmail.com with ESMTPSA id d66-20020a026245000000b0041672c963b3sm656062jac.50.2023.05.18.13.02.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 May 2023 13:02:22 -0700 (PDT) Date: Thu, 18 May 2023 14:02:20 -0600 From: Alex Williamson To: "Liu, Yi L" Cc: "jgg@nvidia.com" , "Tian, Kevin" , "joro@8bytes.org" , "robin.murphy@arm.com" , "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.y.sun@linux.intel.com" , "peterx@redhat.com" , "jasowang@redhat.com" , "shameerali.kolothum.thodi@huawei.com" , "lulu@redhat.com" , "suravee.suthikulpanit@amd.com" , "intel-gvt-dev@lists.freedesktop.org" , "intel-gfx@lists.freedesktop.org" , "linux-s390@vger.kernel.org" , "Hao, Xudong" , "Zhao, Yan Y" , "Xu, Terrence" , "Jiang, Yanting" , "Duan, Zhenzhong" , "clegoate@redhat.com" Subject: Re: [PATCH v5 09/10] vfio/pci: Extend VFIO_DEVICE_GET_PCI_HOT_RESET_INFO for vfio device cdev Message-ID: <20230518140220.0953074c.alex.williamson@redhat.com> In-Reply-To: References: <20230513132136.15021-1-yi.l.liu@intel.com> <20230513132136.15021-10-yi.l.liu@intel.com> <20230517160131.254be76b.alex.williamson@redhat.com> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.35; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-s390@vger.kernel.org On Thu, 18 May 2023 13:21:57 +0000 "Liu, Yi L" wrote: > > From: Alex Williamson > > Sent: Thursday, May 18, 2023 6:02 AM > >=20 > > On Sat, 13 May 2023 06:21:35 -0700 > > Yi Liu wrote: > > =20 > > > This makes VFIO_DEVICE_GET_PCI_HOT_RESET_INFO ioctl to use the iommuf= d_ctx =20 > >=20 > > s/makes/allows/? > >=20 > > s/to// > > =20 > > > of the cdev device to check the ownership of the other affected devic= es. > > > > > > This returns devid for each of the affected devices. If it is bound t= o the > > > iommufd_ctx of the cdev device, _INFO reports a valid devid > 0; If i= t is > > > not opened by the calling user, but it belongs to the same iommu_grou= p of > > > a device that is bound to the iommufd_ctx of the cdev device, reports= devid > > > value of 0; If the device is un-owned device, configured within a dif= ferent > > > iommufd, or opened outside of the vfio device cdev API, the _INFO ioc= tl shall > > > report devid value of -1. > > > > > > devid >=3D0 doesn't block hot-reset as the affected devices are consi= dered to > > > be owned, while devid =3D=3D -1 will block the use of VFIO_DEVICE_PCI= _HOT_RESET > > > outside of proof-of-ownership calling conventions (ie. via legacy gro= up > > > accessed devices). > > > > > > This adds flag VFIO_PCI_HOT_RESET_FLAG_DEV_ID to tell the user devid = is > > > returned in case of calling user get device fd from other software st= ack =20 > >=20 > > "other software stack"? I think this is trying to say something like: > >=20 > > When VFIO_DEVICE_GET_PCI_HOT_RESET_INFO is called on an IOMMUFD > > managed device, the new flag VFIO_PCI_HOT_RESET_FLAG_DEV_ID is > > reported to indicate the values returned are IOMMUFD devids rather > > than group IDs as used when accessing vfio devices through the > > conventional vfio group interface. Additionally the flag > > VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED will be reported in this mode if > > all of the devices affected by the hot-reset are owned by either > > virtue of being directly bound to the same iommufd context as the > > calling device, or implicitly owned via a shared IOMMU group. =20 >=20 > Yes. it is. >=20 > > > and adds flag VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED to tell user if all > > > the affected devices are owned, so user can know it without looping a= ll > > > the returned devids. > > > > > > Suggested-by: Jason Gunthorpe > > > Suggested-by: Alex Williamson > > > Signed-off-by: Yi Liu > > > --- > > > drivers/vfio/pci/vfio_pci_core.c | 52 ++++++++++++++++++++++++++++++= -- > > > include/uapi/linux/vfio.h | 46 +++++++++++++++++++++++++++- > > > 2 files changed, 95 insertions(+), 3 deletions(-) > > > > > > diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio= _pci_core.c > > > index 4df2def35bdd..57586be770af 100644 > > > --- a/drivers/vfio/pci/vfio_pci_core.c > > > +++ b/drivers/vfio/pci/vfio_pci_core.c > > > @@ -27,6 +27,7 @@ > > > #include > > > #include > > > #include > > > +#include > > > #if IS_ENABLED(CONFIG_EEH) > > > #include > > > #endif > > > @@ -36,6 +37,10 @@ > > > #define DRIVER_AUTHOR "Alex Williamson " > > > #define DRIVER_DESC "core driver for VFIO based PCI devices" > > > > > > +#ifdef CONFIG_IOMMUFD > > > +MODULE_IMPORT_NS(IOMMUFD); > > > +#endif > > > + > > > static bool nointxmask; > > > static bool disable_vga; > > > static bool disable_idle_d3; > > > @@ -776,6 +781,9 @@ struct vfio_pci_fill_info { > > > int max; > > > int cur; > > > struct vfio_pci_dependent_device *devices; > > > + struct vfio_device *vdev; > > > + bool devid:1; > > > + bool dev_owned:1; > > > }; > > > > > > static int vfio_pci_fill_devs(struct pci_dev *pdev, void *data) > > > @@ -790,7 +798,37 @@ static int vfio_pci_fill_devs(struct pci_dev *pd= ev, void *data) > > > if (!iommu_group) > > > return -EPERM; /* Cannot reset non-isolated devices */ > > > > > > - fill->devices[fill->cur].group_id =3D iommu_group_id(iommu_group); > > > + if (fill->devid) { > > > + struct iommufd_ctx *iommufd =3D vfio_iommufd_physical_ictx(fill->v= dev); > > > + struct vfio_device_set *dev_set =3D fill->vdev->dev_set; > > > + struct vfio_device *vdev; > > > + > > > + /* > > > + * Report devid for the affected devices: > > > + * - valid devid > 0 for the devices that are bound with > > > + * the iommufd of the calling device. > > > + * - devid =3D=3D 0 for the devices that have not been opened > > > + * but have same group with one of the devices bound to > > > + * the iommufd of the calling device. > > > + * - devid =3D=3D -1 for others, and clear dev_owned flag. > > > + */ > > > + vdev =3D vfio_find_device_in_devset(dev_set, &pdev->dev); > > > + if (vdev && iommufd =3D=3D vfio_iommufd_physical_ictx(vdev)) { > > > + int ret; > > > + > > > + ret =3D vfio_iommufd_physical_devid(vdev); > > > + if (WARN_ON(ret < 0)) > > > + return ret; > > > + fill->devices[fill->cur].devid =3D ret; =20 > >=20 > > Nit, @devid seems like a better variable name here rather than @ret. > > =20 > > > + } else if (vdev && iommufd_ctx_has_group(iommufd, iommu_group)) { > > > + fill->devices[fill->cur].devid =3D VFIO_PCI_DEVID_OWNED; > > > + } else { > > > + fill->devices[fill->cur].devid =3D VFIO_PCI_DEVID_NOT_OWNED; > > > + fill->dev_owned =3D false; > > > + } =20 > >=20 > > I think we're not describing the requirements for this middle test > > correctly. We're essentially only stating the iommufd_ctx_has_group() > > part of the requirement, but we're also enforcing a > > vfio_find_device_in_devset() requirement, which means the device is not > > just unopened within a group shared by the iommufd context, but it must > > also still be a device registered as a member of the devset, ie. it > > must be bound to a vfio driver. =20 >=20 > Yes. This is to make it be par with hot-reset path. This is needed. Is it? Yes. In supporting this null-array model, the kernel is taking on the responsibility to indicate that the hot-reset is available, which necessarily includes the devset test. I think the logic we have is correct, but the documentation and comments should match the code as well. > > It's not a new requirement, it's imposed in the hot-reset ioctl itself, > > but it's new for the info ioctl given that it's now trying to report > > that the user can perform the reset for cdev callers. > > > > This also shares too much logic with vfio_device_owned() added in the > > next patch. I think it might be cleaner to move the iommu_group_get() = to > > the group path below and change vfio_device_owned() to something that > > can be used here and in the reset path. For example, if we had a > > function like: > >=20 > > static int vfio_hot_reset_devid(struct vfio_device *vdev, > > struct iommufd_ctx *iommufd_ctx) > > { > > struct iommu_group *group; > > int devid; > >=20 > > if (!vdev) > > return VFIO_PCI_DEVID_NOT_OWNED; > >=20 > > if (vfio_iommufd_physical_ictx(vdev) =3D=3D iommufd_ctx) > > return vfio_iommufd_physical_devid(vdev); > >=20 > > group =3D iommu_group_get(vdev->dev); > > if (!group) > > return VFIO_PCI_DEVID_NOT_OWNED; > >=20 > > if (iommufd_ctx_has_group(iommufd_ctx, group)) > > devid =3D VFIO_PCI_DEVID_OWNED; > >=20 > > iommu_group_put(group); > >=20 > > return devid; > > } =20 >=20 > Thanks. This can be placed in vfio/iommufd.c, hence no need to > Import the IOMMUFD namespace in vfio_pci_core.c. > vfio_iommufd_physical_devid() can ebe static within vfio/iommufd.c Good, that's an improvement too. Thanks, Alex =20 > > It could be called above as: > >=20 > > vdev =3D vfio_find_device_in_devset(dev_set, &pdev->dev); > > fill->devices[fill->cur].devid =3D > > vfio_hot_reset_devid(vdev, iommufd); > >=20 > >=20 > > And from vfio_pci_dev_set_hot_reset() as: > >=20 > > bool owned; > >=20 > > if (iommufd_ctx) { > > int devid =3D vfio_hot_reset_devid(&cur_vma->vdev, > > iommufd_ctx); > >=20 > > owned =3D (devid !=3D VFIO_PCI_DEVID_NOT_OWNED); > > } else > > owned =3D vfio_dev_in_groups(&cur_vma->vdev, groups); > >=20 > > Any better? =20 >=20 > Above looks good enough. >=20 > > =20 > > > + } else { > > > + fill->devices[fill->cur].group_id =3D iommu_group_id(iommu_group); > > > + } > > > fill->devices[fill->cur].segment =3D pci_domain_nr(pdev->bus); > > > fill->devices[fill->cur].bus =3D pdev->bus->number; > > > fill->devices[fill->cur].devfn =3D pdev->devfn; > > > @@ -1229,17 +1267,27 @@ static int vfio_pci_ioctl_get_pci_hot_reset_i= nfo( > > > return -ENOMEM; > > > > > > fill.devices =3D devices; > > > + fill.vdev =3D &vdev->vdev; > > > > > > + mutex_lock(&vdev->vdev.dev_set->lock); > > > + fill.devid =3D fill.dev_owned =3D vfio_device_cdev_opened(&vdev->vd= ev); > > > ret =3D vfio_pci_for_each_slot_or_bus(vdev->pdev, vfio_pci_fill_dev= s, > > > &fill, slot); > > > + mutex_unlock(&vdev->vdev.dev_set->lock); > > > > > > /* > > > * If a device was removed between counting and filling, we may com= e up > > > * short of fill.max. If a device was added, we'll have a return of > > > * -EAGAIN above. > > > */ > > > - if (!ret) > > > + if (!ret) { > > > hdr.count =3D fill.cur; > > > + if (fill.devid) { > > > + hdr.flags |=3D VFIO_PCI_HOT_RESET_FLAG_DEV_ID; > > > + if (fill.dev_owned) > > > + hdr.flags |=3D =20 > > VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED; =20 > > > + } > > > + } =20 > >=20 > > Does this clean up the flag and branching a bit? =20 >=20 > Yes. =F0=9F=98=8A >=20 > >=20 > > diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_p= ci_core.c > > index 737115d16a79..6a2a079e452d 100644 > > --- a/drivers/vfio/pci/vfio_pci_core.c > > +++ b/drivers/vfio/pci/vfio_pci_core.c > > @@ -786,8 +786,7 @@ struct vfio_pci_fill_info { > > int cur; > > struct vfio_pci_dependent_device *devices; > > struct vfio_device *vdev; > > - bool devid:1; > > - bool dev_owned:1; > > + u32 flags; > > }; > >=20 > > static int vfio_pci_fill_devs(struct pci_dev *pdev, void *data) > > @@ -802,7 +801,7 @@ static int vfio_pci_fill_devs(struct pci_dev *pdev,= void *data) > > if (!iommu_group) > > return -EPERM; /* Cannot reset non-isolated devices */ > >=20 > > - if (fill->devid) { > > + if (fill->flags & VFIO_PCI_HOT_RESET_FLAG_DEV_ID) { > > struct iommufd_ctx *iommufd =3D vfio_iommufd_physical_ictx(fill->vde= v); > > struct vfio_device_set *dev_set =3D fill->vdev->dev_set; > > struct vfio_device *vdev; > > @@ -814,7 +813,7 @@ static int vfio_pci_fill_devs(struct pci_dev *pdev,= void *data) > > * - devid =3D=3D 0 for the devices that have not been opened > > * but have same group with one of the devices bound to > > * the iommufd of the calling device. > > - * - devid =3D=3D -1 for others, and clear dev_owned flag. > > + * - devid =3D=3D -1 for others, and clear owned flag. > > */ > > vdev =3D vfio_find_device_in_devset(dev_set, &pdev->dev); > > if (vdev && iommufd =3D=3D vfio_iommufd_physical_ictx(vdev)) { > > @@ -828,7 +827,7 @@ static int vfio_pci_fill_devs(struct pci_dev *pdev,= void *data) > > fill->devices[fill->cur].devid =3D VFIO_PCI_DEVID_OWNED; > > } else { > > fill->devices[fill->cur].devid =3D VFIO_PCI_DEVID_NOT_OWNED; > > - fill->dev_owned =3D false; > > + fill->flags &=3D ~VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED; > > } > > } else { > > fill->devices[fill->cur].group_id =3D iommu_group_id(iommu_group); > > @@ -1273,8 +1272,11 @@ static int vfio_pci_ioctl_get_pci_hot_reset_info( > > fill.devices =3D devices; > > fill.vdev =3D &vdev->vdev; > >=20 > > + if (vfio_device_cdev_opened(&vdev->vdev)) > > + fill.flags |=3D VFIO_PCI_HOT_RESET_FLAG_DEV_ID | > > + VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED; > > + > > mutex_lock(&vdev->vdev.dev_set->lock); > > - fill.devid =3D fill.dev_owned =3D vfio_device_cdev_opened(&vdev->vdev= ); > > ret =3D vfio_pci_for_each_slot_or_bus(vdev->pdev, vfio_pci_fill_devs, > > &fill, slot); > > mutex_unlock(&vdev->vdev.dev_set->lock); > > @@ -1286,11 +1288,7 @@ static int vfio_pci_ioctl_get_pci_hot_reset_info( > > */ > > if (!ret) { > > hdr.count =3D fill.cur; > > - if (fill.devid) { > > - hdr.flags |=3D VFIO_PCI_HOT_RESET_FLAG_DEV_ID; > > - if (fill.dev_owned) > > - hdr.flags |=3D > > VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED; > > - } > > + hdr.flags =3D fill.flags; > > } > >=20 > > reset_info_exit: > >=20 > > Thanks, > > Alex =20 >=20 > Thanks, > Yi Liu >=20 > > > > > > reset_info_exit: > > > if (copy_to_user(arg, &hdr, minsz)) > > > diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h > > > index 0552e8dcf0cb..01203215251a 100644 > > > --- a/include/uapi/linux/vfio.h > > > +++ b/include/uapi/linux/vfio.h > > > @@ -650,11 +650,53 @@ enum { > > > * VFIO_DEVICE_GET_PCI_HOT_RESET_INFO - _IOWR(VFIO_TYPE, VFIO_BASE += 12, > > > * struct vfio_pci_hot_reset_info) > > > * > > > + * This command is used to query the affected devices in the hot res= et for > > > + * a given device. > > > + * > > > + * This command always reports the segment, bus, and devfn informati= on for > > > + * each affected device, and selectively reports the group_id or dev= id per > > > + * the way how the calling device is opened. > > > + * > > > + * - If the calling device is opened via the traditional group/conta= iner > > > + * API, group_id is reported. User should check if it has owned a= ll > > > + * the affected devices and provides a set of group fds to prove t= he > > > + * ownership in VFIO_DEVICE_PCI_HOT_RESET ioctl. > > > + * > > > + * - If the calling device is opened as a cdev, devid is reported. > > > + * Flag VFIO_PCI_HOT_RESET_FLAG_DEV_ID is set to indicate this > > > + * data type. For a given affected device, it is considered owned= by > > > + * this interface if it meets the following conditions: > > > + * 1) Has a valid devid within the iommufd_ctx of the calling devi= ce. > > > + * Ownership cannot be determined across separate iommufd_ctx a= nd the > > > + * cdev calling conventions do not support a proof-of-ownership= model > > > + * as provided in the legacy group interface. In this case a v= alid > > > + * devid with value greater than zero is provided in the return > > > + * structure. > > > + * 2) Does not have a valid devid within the iommufd_ctx of the ca= lling > > > + * device, but belongs to the same IOMMU group as the calling d= evice > > > + * or another opened device that has a valid devid within the > > > + * iommufd_ctx of the calling device. This provides implicit o= wnership > > > + * for devices within the same DMA isolation context. In this = case > > > + * the invalid devid value of zero is provided in the return st= ructure. > > > + * > > > + * A devid value of -1 is provided in the return structure for dev= ices > > > + * where ownership is not available. Such devices prevent the use= of > > > + * VFIO_DEVICE_PCI_HOT_RESET outside of proof-of-ownership calling > > > + * conventions (ie. via legacy group accessed devices). > > > + * Flag VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED would be set when all= the > > > + * affected devices are owned by the user. This flag is available= only > > > + * when VFIO_PCI_HOT_RESET_FLAG_DEV_ID is set, otherwise reserved. > > > + * > > > * Return: 0 on success, -errno on failure: > > > * -enospc =3D insufficient buffer, -enodev =3D unsupported for devi= ce. > > > */ > > > struct vfio_pci_dependent_device { > > > - __u32 group_id; > > > + union { > > > + __u32 group_id; > > > + __u32 devid; > > > +#define VFIO_PCI_DEVID_OWNED 0 > > > +#define VFIO_PCI_DEVID_NOT_OWNED -1 > > > + }; > > > __u16 segment; > > > __u8 bus; > > > __u8 devfn; /* Use PCI_SLOT/PCI_FUNC */ > > > @@ -663,6 +705,8 @@ struct vfio_pci_dependent_device { > > > struct vfio_pci_hot_reset_info { > > > __u32 argsz; > > > __u32 flags; > > > +#define VFIO_PCI_HOT_RESET_FLAG_DEV_ID (1 << 0) > > > +#define VFIO_PCI_HOT_RESET_FLAG_DEV_ID_OWNED (1 << 1) > > > __u32 count; > > > struct vfio_pci_dependent_device devices[]; > > > }; =20 >=20