search for: get_region_info

[cut] > > So overall the interface and extension makes sense. My only question is > > whether it's better to get complete reuse out of GET_REGION_INFO and > > GET_IRQ_INFO and then add another device tree specific ioctl or is it > > better to add a device tree index and path to the existing GET_*_INFO > > ioctls? Getting some information from one ioctl and passing pieces of > > it back to another ioctl feels a little clun...

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

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

...eturns 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...

...evice. 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...

...evice. 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...