search for: vfio_device_get_info

Displaying 20 results from an estimated 24 matches for "vfio_device_get_info".

2013 Jul 02
7
RFC: vfio interface for platform devices
...ecific platform device path to get the device information: fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); (whether the path is a device tree path or a sysfs path is up for discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") 2. VFIO_DEVICE_GET_INFO Don't think any changes are needed to VFIO_DEVICE_GET_INFO other than adding a new flag identifying a devices as a 'platform' device. This ioctl simply returns the number of regions and number of irqs. The number of regions corresponds to the number of regions that...
2013 Jul 02
7
RFC: vfio interface for platform devices
...ecific platform device path to get the device information: fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); (whether the path is a device tree path or a sysfs path is up for discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") 2. VFIO_DEVICE_GET_INFO Don't think any changes are needed to VFIO_DEVICE_GET_INFO other than adding a new flag identifying a devices as a 'platform' device. This ioctl simply returns the number of regions and number of irqs. The number of regions corresponds to the number of regions that...
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
Version 2 -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, defined 5 new flags and associated structs -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, defined 1 new flag and associate...
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
Version 2 -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, defined 5 new flags and associated structs -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, defined 1 new flag and associate...
2013 Jul 03
0
RFC: vfio interface for platform devices
...get the device information: > > fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); > > (whether the path is a device tree path or a sysfs path is up for > discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") > > 2. VFIO_DEVICE_GET_INFO > > Don't think any changes are needed to VFIO_DEVICE_GET_INFO other > than adding a new flag identifying a devices as a 'platform' > device. > > This ioctl simply returns the number of regions and number of irqs. > > The number of regions correspond...
2013 Jul 03
0
RFC: vfio interface for platform devices
...t the device information: > > fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); > > (whether the path is a device tree path or a sysfs path is up for > discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") > > 2. VFIO_DEVICE_GET_INFO > > Don't think any changes are needed to VFIO_DEVICE_GET_INFO other > than adding a new flag identifying a devices as a 'platform' > device. > > This ioctl simply returns the number of regions and number of irqs. > > The number of regions corre...
2013 Jul 04
0
RFC: vfio interface for platform devices (v2)
...e the Guest Device Model != Host. How do you inform the guest where the device is mapped in its physical address space, and handle GPA faults? - Mario On 7/3/2013 11:40 PM, Yoder Stuart-B08248 wrote: > Version 2 > -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path > -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 > -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl > -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, > defined 5 new flags and associated structs > -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, > defined...
2013 Jul 03
0
RFC: vfio interface for platform devices (v2)
On Wed, 2013-07-03 at 21:40 +0000, Yoder Stuart-B08248 wrote: > Version 2 > -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path > -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 > -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl > -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, > defined 5 new flags and associated structs > -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, > defined...
2013 Jul 03
1
RFC: vfio interface for platform devices
...>> >> fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); >> >> (whether the path is a device tree path or a sysfs path is up for >> discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") >> >> 2. VFIO_DEVICE_GET_INFO >> >> Don't think any changes are needed to VFIO_DEVICE_GET_INFO other >> than adding a new flag identifying a devices as a 'platform' >> device. >> >> This ioctl simply returns the number of regions and number of irqs. >> >>...
2013 Jul 03
1
RFC: vfio interface for platform devices
...>> >> fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); >> >> (whether the path is a device tree path or a sysfs path is up for >> discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") >> >> 2. VFIO_DEVICE_GET_INFO >> >> Don't think any changes are needed to VFIO_DEVICE_GET_INFO other >> than adding a new flag identifying a devices as a 'platform' >> device. >> >> This ioctl simply returns the number of regions and number of irqs. >> >>...
2013 Jul 03
0
RFC: vfio interface for platform devices
...ces/ffe210000.usb") Doesn't VFIO need to operate on an actual Linux device, rather than just an OF node? Are we going to have a fixed assumption that you always want all the children of the node corresponding to the assigned device, or will it be possible to exclude some? > 2. VFIO_DEVICE_GET_INFO > > Don't think any changes are needed to VFIO_DEVICE_GET_INFO other > than adding a new flag identifying a devices as a 'platform' > device. > > This ioctl simply returns the number of regions and number of irqs. > > The number of regions corre...
2019 Sep 03
2
[RFC v3] vhost: introduce mdev based hardware vhost backend
...+ void __user *argp = (void __user *)arg; > + struct vhost_mdev *vdpa; > + unsigned long minsz; > + int ret = 0; > + > + if (!mdev) > + return -EINVAL; > + > + vdpa = mdev_get_drvdata(mdev); > + if (!vdpa) > + return -ENODEV; > + > + switch (cmd) { > + case VFIO_DEVICE_GET_INFO: > + { > + struct vfio_device_info info; > + > + minsz = offsetofend(struct vfio_device_info, num_irqs); > + > + if (copy_from_user(&info, (void __user *)arg, minsz)) { > + ret = -EFAULT; > + break; > + } > + > + if (info.argsz < minsz) { > + re...
2019 Sep 03
2
[RFC v3] vhost: introduce mdev based hardware vhost backend
...+ void __user *argp = (void __user *)arg; > + struct vhost_mdev *vdpa; > + unsigned long minsz; > + int ret = 0; > + > + if (!mdev) > + return -EINVAL; > + > + vdpa = mdev_get_drvdata(mdev); > + if (!vdpa) > + return -ENODEV; > + > + switch (cmd) { > + case VFIO_DEVICE_GET_INFO: > + { > + struct vfio_device_info info; > + > + minsz = offsetofend(struct vfio_device_info, num_irqs); > + > + if (copy_from_user(&info, (void __user *)arg, minsz)) { > + ret = -EFAULT; > + break; > + } > + > + if (info.argsz < minsz) { > + re...
2013 Jul 16
2
RFC: vfio interface for platform devices
...; Are we going to have a fixed assumption that you always want all the > children of the node corresponding to the assigned device, or will it > be possible to exclude some? My assumption is that you always get all the children of the node corresponding to the assigned device. > > 2. VFIO_DEVICE_GET_INFO > > > > Don't think any changes are needed to VFIO_DEVICE_GET_INFO other > > than adding a new flag identifying a devices as a 'platform' > > device. > > > > This ioctl simply returns the number of regions and number of irqs. > > &gt...
2013 Jul 16
2
RFC: vfio interface for platform devices
...; Are we going to have a fixed assumption that you always want all the > children of the node corresponding to the assigned device, or will it > be possible to exclude some? My assumption is that you always get all the children of the node corresponding to the assigned device. > > 2. VFIO_DEVICE_GET_INFO > > > > Don't think any changes are needed to VFIO_DEVICE_GET_INFO other > > than adding a new flag identifying a devices as a 'platform' > > device. > > > > This ioctl simply returns the number of regions and number of irqs. > > &gt...
2019 Sep 04
0
[RFC v3] vhost: introduce mdev based hardware vhost backend
...st_mdev *vdpa; > > + unsigned long minsz; > > + int ret = 0; > > + > > + if (!mdev) > > + return -EINVAL; > > + > > + vdpa = mdev_get_drvdata(mdev); > > + if (!vdpa) > > + return -ENODEV; > > + > > + switch (cmd) { > > + case VFIO_DEVICE_GET_INFO: > > + { > > + struct vfio_device_info info; > > + > > + minsz = offsetofend(struct vfio_device_info, num_irqs); > > + > > + if (copy_from_user(&info, (void __user *)arg, minsz)) { > > + ret = -EFAULT; > > + break; > > + } > >...
2019 Jul 03
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...unsigned int cmd, unsigned long arg) > +{ > + int ret = 0; > + unsigned long minsz; > + struct vdpa_dev *vdpa; > + > + if (!mdev) > + return -EINVAL; > + > + vdpa = mdev_get_drvdata(mdev); > + if (!vdpa) > + return -ENODEV; > + > + switch (cmd) { > + case VFIO_DEVICE_GET_INFO: > + { > + struct vfio_device_info info; > + > + minsz = offsetofend(struct vfio_device_info, num_irqs); > + > + if (copy_from_user(&info, (void __user *)arg, minsz)) > + return -EFAULT; > + > + if (info.argsz < minsz) > + return -EINVAL; > + > +...
2019 Jul 03
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...: -1); + + return 0; +} + +long vdpa_ioctl(struct mdev_device *mdev, unsigned int cmd, unsigned long arg) +{ + int ret = 0; + unsigned long minsz; + struct vdpa_dev *vdpa; + + if (!mdev) + return -EINVAL; + + vdpa = mdev_get_drvdata(mdev); + if (!vdpa) + return -ENODEV; + + switch (cmd) { + case VFIO_DEVICE_GET_INFO: + { + struct vfio_device_info info; + + minsz = offsetofend(struct vfio_device_info, num_irqs); + + if (copy_from_user(&info, (void __user *)arg, minsz)) + return -EFAULT; + + if (info.argsz < minsz) + return -EINVAL; + + ret = vdpa_get_device_info(mdev, &info); + if (ret) +...
2019 Jul 03
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...: -1); + + return 0; +} + +long vdpa_ioctl(struct mdev_device *mdev, unsigned int cmd, unsigned long arg) +{ + int ret = 0; + unsigned long minsz; + struct vdpa_dev *vdpa; + + if (!mdev) + return -EINVAL; + + vdpa = mdev_get_drvdata(mdev); + if (!vdpa) + return -ENODEV; + + switch (cmd) { + case VFIO_DEVICE_GET_INFO: + { + struct vfio_device_info info; + + minsz = offsetofend(struct vfio_device_info, num_irqs); + + if (copy_from_user(&info, (void __user *)arg, minsz)) + return -EFAULT; + + if (info.argsz < minsz) + return -EINVAL; + + ret = vdpa_get_device_info(mdev, &info); + if (ret) +...
2018 Apr 10
0
[RFC] vhost: introduce mdev based hardware vhost backend
...unsigned int cmd, unsigned long arg) > +{ > + int ret = 0; > + unsigned long minsz; > + struct vdpa_dev *vdpa; > + > + if (!mdev) > + return -EINVAL; > + > + vdpa = mdev_get_drvdata(mdev); > + if (!vdpa) > + return -ENODEV; > + > + switch (cmd) { > + case VFIO_DEVICE_GET_INFO: > + { > + struct vfio_device_info info; > + > + minsz = offsetofend(struct vfio_device_info, num_irqs); > + > + if (copy_from_user(&info, (void __user *)arg, minsz)) > + return -EFAULT; > + > + if (info.argsz < minsz) > + return -EINVAL; > + > +...