search for: vfio_device_get_region_info

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 associated struct -removed redundant example ---------------------------------------------------------------------...

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 associated struct -removed redundant example ---------------------------------------------------------------------...

...s 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 1 new flag and associated struct > -removed redundant example > > ---------------------------------------...

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 1 new flag and associated struct > -removed redundant example > > ---------------------------------------...

...rm' device. This ioctl simply returns the number of regions and number of irqs. The number of regions corresponds to the number of regions that can be mapped for the device-- corresponds to the regions defined in "reg" and "ranges" in the device tree. 3. VFIO_DEVICE_GET_REGION_INFO No changes needed, except perhaps adding a new flag. Freescale has some devices with regions that must be mapped cacheable. 3. VFIO_DEVICE_GET_IRQ_INFO No changes needed. 4. VFIO_DEVICE_GET_DEVTREE_INFO The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs expose d...

...rm' device. This ioctl simply returns the number of regions and number of irqs. The number of regions corresponds to the number of regions that can be mapped for the device-- corresponds to the regions defined in "reg" and "ranges" in the device tree. 3. VFIO_DEVICE_GET_REGION_INFO No changes needed, except perhaps adding a new flag. Freescale has some devices with regions that must be mapped cacheable. 3. VFIO_DEVICE_GET_IRQ_INFO No changes needed. 4. VFIO_DEVICE_GET_DEVTREE_INFO The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs expose d...

...ctl simply returns the number of regions and number of irqs. > > The number of regions corresponds to the number of regions > that can be mapped for the device-- corresponds to the regions defined > in "reg" and "ranges" in the device tree. > > 3. VFIO_DEVICE_GET_REGION_INFO > > No changes needed, except perhaps adding a new flag. Freescale has some > devices with regions that must be mapped cacheable. > > 3. VFIO_DEVICE_GET_IRQ_INFO > > No changes needed. > > 4. VFIO_DEVICE_GET_DEVTREE_INFO > > The VFIO_DEVICE_GET_RE...

...ioctl simply returns the number of regions and number of irqs. > > The number of regions corresponds to the number of regions > that can be mapped for the device-- corresponds to the regions defined > in "reg" and "ranges" in the device tree. > > 3. VFIO_DEVICE_GET_REGION_INFO > > No changes needed, except perhaps adding a new flag. Freescale has some > devices with regions that must be mapped cacheable. > > 3. VFIO_DEVICE_GET_IRQ_INFO > > No changes needed. > > 4. VFIO_DEVICE_GET_DEVTREE_INFO > > The VFIO_DEVICE_GET_REGION...

...he number of regions and number of irqs. >> >> The number of regions corresponds to the number of regions >> that can be mapped for the device-- corresponds to the regions defined >> in "reg" and "ranges" in the device tree. >> >> 3. VFIO_DEVICE_GET_REGION_INFO >> >> No changes needed, except perhaps adding a new flag. Freescale has some >> devices with regions that must be mapped cacheable. >> >> 3. VFIO_DEVICE_GET_IRQ_INFO >> >> No changes needed. >> >> 4. VFIO_DEVICE_GET_DEVTREE_INFO >...

...he number of regions and number of irqs. >> >> The number of regions corresponds to the number of regions >> that can be mapped for the device-- corresponds to the regions defined >> in "reg" and "ranges" in the device tree. >> >> 3. VFIO_DEVICE_GET_REGION_INFO >> >> No changes needed, except perhaps adding a new flag. Freescale has some >> devices with regions that must be mapped cacheable. >> >> 3. VFIO_DEVICE_GET_IRQ_INFO >> >> No changes needed. >> >> 4. VFIO_DEVICE_GET_DEVTREE_INFO >...

...ions and number of irqs. > > > > The number of regions corresponds to the number of regions > > that can be mapped for the device-- corresponds to the regions > > defined > > in "reg" and "ranges" in the device tree. > > > > 3. VFIO_DEVICE_GET_REGION_INFO > > > > No changes needed, except perhaps adding a new flag. Freescale > > has some > > devices with regions that must be mapped cacheable. > > While I don't object to making the information available to the user > just in case, the main thing we need he...

...ions and number of irqs. > > > > The number of regions corresponds to the number of regions > > that can be mapped for the device-- corresponds to the regions > > defined > > in "reg" and "ranges" in the device tree. > > > > 3. VFIO_DEVICE_GET_REGION_INFO > > > > No changes needed, except perhaps adding a new flag. Freescale > > has some > > devices with regions that must be mapped cacheable. > > While I don't object to making the information available to the user > just in case, the main thing we need he...

...imply returns the number of regions and number of irqs. > > The number of regions corresponds to the number of regions > that can be mapped for the device-- corresponds to the regions > defined > in "reg" and "ranges" in the device tree. > > 3. VFIO_DEVICE_GET_REGION_INFO > > No changes needed, except perhaps adding a new flag. Freescale > has some > devices with regions that must be mapped cacheable. While I don't object to making the information available to the user just in case, the main thing we need here is to influence what the...

...t; + break; > + } > + > + info.flags = VFIO_DEVICE_FLAGS_VHOST; > + info.num_regions = 0; > + info.num_irqs = 0; > + > + if (copy_to_user((void __user *)arg, &info, minsz)) { > + ret = -EFAULT; > + break; > + } > + > + break; > + } > + case VFIO_DEVICE_GET_REGION_INFO: > + case VFIO_DEVICE_GET_IRQ_INFO: > + case VFIO_DEVICE_SET_IRQS: > + case VFIO_DEVICE_RESET: > + ret = -EINVAL; > + break; > + > + case VHOST_MDEV_SET_STATE: > + ret = vhost_set_state(vdpa, argp); > + break; > + case VHOST_GET_FEATURES: > + ret = vhost_get_fe...

...t; + break; > + } > + > + info.flags = VFIO_DEVICE_FLAGS_VHOST; > + info.num_regions = 0; > + info.num_irqs = 0; > + > + if (copy_to_user((void __user *)arg, &info, minsz)) { > + ret = -EFAULT; > + break; > + } > + > + break; > + } > + case VFIO_DEVICE_GET_REGION_INFO: > + case VFIO_DEVICE_GET_IRQ_INFO: > + case VFIO_DEVICE_SET_IRQS: > + case VFIO_DEVICE_RESET: > + ret = -EINVAL; > + break; > + > + case VHOST_MDEV_SET_STATE: > + ret = vhost_set_state(vdpa, argp); > + break; > + case VHOST_GET_FEATURES: > + ret = vhost_get_fe...

...t; + break; > + } > + > + info.flags = VFIO_DEVICE_FLAGS_VHOST; > + info.num_regions = 0; > + info.num_irqs = 0; > + > + if (copy_to_user((void __user *)arg, &info, minsz)) { > + ret = -EFAULT; > + break; > + } > + > + break; > + } > + case VFIO_DEVICE_GET_REGION_INFO: > + case VFIO_DEVICE_GET_IRQ_INFO: > + case VFIO_DEVICE_SET_IRQS: > + case VFIO_DEVICE_RESET: > + ret = -EINVAL; > + break; > + > + case VHOST_MDEV_SET_STATE: > + ret = vhost_set_state(vdpa, argp); > + break; So this is used to start or stop the device. This means...

...t; + break; > + } > + > + info.flags = VFIO_DEVICE_FLAGS_VHOST; > + info.num_regions = 0; > + info.num_irqs = 0; > + > + if (copy_to_user((void __user *)arg, &info, minsz)) { > + ret = -EFAULT; > + break; > + } > + > + break; > + } > + case VFIO_DEVICE_GET_REGION_INFO: > + case VFIO_DEVICE_GET_IRQ_INFO: > + case VFIO_DEVICE_SET_IRQS: > + case VFIO_DEVICE_RESET: > + ret = -EINVAL; > + break; > + > + case VHOST_MDEV_SET_STATE: > + ret = vhost_set_state(vdpa, argp); > + break; So this is used to start or stop the device. This means...

...uapi/linux/vfio.h | 2 + > > include/uapi/linux/vhost.h | 8 + > > 6 files changed, 462 insertions(+) > > create mode 100644 drivers/vhost/mdev.c > > create mode 100644 include/linux/vhost_mdev.h [...] > > + > > + break; > > + } > > + case VFIO_DEVICE_GET_REGION_INFO: > > + case VFIO_DEVICE_GET_IRQ_INFO: > > + case VFIO_DEVICE_SET_IRQS: > > + case VFIO_DEVICE_RESET: > > + ret = -EINVAL; > > + break; > > + > > + case VHOST_MDEV_SET_STATE: > > + ret = vhost_set_state(vdpa, argp); > > + break; > > &...

...fio_device_info { > #define VFIO_DEVICE_API_AMBA_STRING "vfio-amba" > #define VFIO_DEVICE_API_CCW_STRING "vfio-ccw" > #define VFIO_DEVICE_API_AP_STRING "vfio-ap" > +#define VFIO_DEVICE_API_VHOST_STRING "vfio-vhost" > > /** > * VFIO_DEVICE_GET_REGION_INFO - _IOWR(VFIO_TYPE, VFIO_BASE + 8, > @@ -573,6 +575,23 @@ enum { > VFIO_CCW_NUM_IRQS > }; > > +/* > + * The vfio-vhost bus driver makes use of the following fixed region and > + * IRQ index mapping. Unimplemented regions return a size of zero. > + * Unimplemented IRQ typ...

On 07/16/2013 04:51:12 PM, Yoder Stuart-B08248 wrote: > > > 3. VFIO_DEVICE_GET_REGION_INFO > > > > > > No changes needed, except perhaps adding a new flag. Freescale > > > has some > > > devices with regions that must be mapped cacheable. > > > > While I don't object to making the information available to the user > > just...