search for: vfio_index

...1 - get devtree info for an > irq > */ > __u32 start; /* output: identifies the index > within the reg/ranges */ "start" is an odd name for this. I'd rename "index" to "vfio_index" and this to "dt_index". > __u8 path[]; /* output: Full path to associated > device tree node */ How does the caller know what size buffer to supply for this? > The VFIO_DEVICE_GET_DEVTREE_INFO ioctl would return: > > -for region in...

...1 - get devtree info for an > > irq > > */ > > __u32 start; /* output: identifies the index > > within the reg/ranges */ > > "start" is an odd name for this. I'd rename "index" to "vfio_index" > and this to "dt_index". > > > __u8 path[]; /* output: Full path to associated > > device tree node */ > > How does the caller know what size buffer to supply for this? > > > The VFIO_DEVICE_GET_DEVTREE_INFO ioctl would ret...

...1 - get devtree info for an > > irq > > */ > > __u32 start; /* output: identifies the index > > within the reg/ranges */ > > "start" is an odd name for this. I'd rename "index" to "vfio_index" > and this to "dt_index". > > > __u8 path[]; /* output: Full path to associated > > device tree node */ > > How does the caller know what size buffer to supply for this? > > > The VFIO_DEVICE_GET_DEVTREE_INFO ioctl would ret...

The write-up below is the first draft of a proposal for how the kernel can expose platform devices to user space using vfio. In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which allows user space to correlate regions and interrupts to the corresponding device tree node structure that is defined for most platform devices. Regards, Stuart Yoder

The write-up below is the first draft of a proposal for how the kernel can expose platform devices to user space using vfio. In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which allows user space to correlate regions and interrupts to the corresponding device tree node structure that is defined for most platform devices. Regards, Stuart Yoder