search for: vfio_device_get_irq_info

...rsion 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 ------------------------------------------------------------------------------ VFIO for Platform Devices The existing kernel interface for vfio-pci is pretty close to what is needed f...

...rsion 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 ------------------------------------------------------------------------------ VFIO for Platform Devices The existing kernel interface for vfio-pci is pretty close to what is needed f...

...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 device regions and interrupts, but it's not enough to know that there are X regions and Y interrupts. User space needs to know what the resources are fo...

...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 device regions and interrupts, but it's not enough to know that there are X regions and Y interrupts. User space needs to know what the resources are fo...

...ds 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 device regions and interrupts, but it's not enough to know > that there are X regions and Y interrupts. User space needs...

...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 device regions and interrupts, but it's not enough to know > that there are X regions and Y interrupts. User space ne...

..._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 > > ------------------------------------------------------------------------------ > VFIO for Platform Devices > > The existing kernel interface for vfio-pci...

..._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 > > ------------------------------------------------------------------------------ > VFIO for Platform Devices > > The existing kernel interface for vfio-pci...

...> 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 device regions and interrupts, but it's not enough to know >> that there are X regions and...

...> 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 device regions and interrupts, but it's not enough to know >> that there are X regions and...

...fo.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_features(vdpa, argp); > + break; &gt...

...fo.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_features(vdpa, argp); > + break; &gt...

...gions = 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 =...

...o the user just in case, the main thing we need here is to influence what the kernel does when the user tries to map it. At least on PPC it's not up to userspace to select whether a mmap is cacheable. > 4. VFIO_DEVICE_GET_DEVTREE_INFO > > The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs > expose device regions and interrupts, but it's not enough to know > that there are X regions and Y interrupts. User space needs to > know what the resources are for-- to correlate those > regions/interrupts > to the device tree structure that drivers use. T...

...fo.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 if userspace want to drive a network...

...fo.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 if userspace want to drive a network...

.../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; > > > So this is used to start or stop the de...

...pace really can't do anything with the 'cacheable' flag, do you think there is good reason to keep it? Will it help any decision that user space makes? Maybe we should just drop it. > > 4. VFIO_DEVICE_GET_DEVTREE_INFO > > > > The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs > > expose device regions and interrupts, but it's not enough to know > > that there are X regions and Y interrupts. User space needs to > > know what the resources are for-- to correlate those > > regions/interrupts > > to the device tree structu...

...pace really can't do anything with the 'cacheable' flag, do you think there is good reason to keep it? Will it help any decision that user space makes? Maybe we should just drop it. > > 4. VFIO_DEVICE_GET_DEVTREE_INFO > > > > The VFIO_DEVICE_GET_REGION_INFO and VFIO_DEVICE_GET_IRQ_INFO APIs > > expose device regions and interrupts, but it's not enough to know > > that there are X regions and Y interrupts. User space needs to > > know what the resources are for-- to correlate those > > regions/interrupts > > to the device tree structu...

...urn -EINVAL; > + > + ret = vdpa_get_region_info(mdev, &info, &cap_type_id, > + &cap_type); > + if (ret) > + return ret; > + > + if (copy_to_user((void __user *)arg, &info, minsz)) > + return -EFAULT; > + > + return 0; > + } > + case VFIO_DEVICE_GET_IRQ_INFO: > + { > + struct vfio_irq_info info; > + > + minsz = offsetofend(struct vfio_irq_info, count); > + > + if (copy_from_user(&info, (void __user *)arg, minsz)) > + return -EFAULT; > + > + if (info.argsz < minsz || info.index >= vdpa->max_vrings) > +...