search for: vfio_devtree_region_info_flag_path

...__u32 argsz; __u32 flags; #define VFIO_REGION_INFO_FLAG_CACHEABLE (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_REG (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) __u32 index; /* Region index */ __u32 resv; /* Reserved for alignment */ __u64 size; /* Region size (bytes) */ __u64 offset; /* Region offset from start of device fd */ }; VFIO_REGION_INFO_FLAG_CACHE...

...__u32 argsz; __u32 flags; #define VFIO_REGION_INFO_FLAG_CACHEABLE (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_REG (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) __u32 index; /* Region index */ __u32 resv; /* Reserved for alignment */ __u64 size; /* Region size (bytes) */ __u64 offset; /* Region offset from start of device fd */ }; VFIO_REGION_INFO_FLAG_CACHE...

...__u32 flags; > #define VFIO_REGION_INFO_FLAG_CACHEABLE (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_REG (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) > __u32 index; /* Region index */ > __u32 resv; /* Reserved for alignment */ > __u64 size; /* Region size (bytes) */ > __u64 offset; /* Region offset from start of device fd */ > }; >...

...__u32 flags; > #define VFIO_REGION_INFO_FLAG_CACHEABLE (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_REG (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) > __u32 index; /* Region index */ > __u32 resv; /* Reserved for alignment */ > __u64 size; /* Region size (bytes) */ > __u64 offset; /* Region offset from start of device fd */ > }; >...

...uire no space: #define VFIO_DEVTREE_REGION_INFO_FLAG_REG (1 << ?) #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) Others imply a structure added to the end: #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) struct vfio_devtree_region_info_index { u32 index; } #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) struct vfio_devtree_region_info_path { u32 len; u8 path[]; } The order of the flags indicates the order of the structures at the end. We'd need to have some rules about alignment, probably always dword aligned. I'm not sure if it would be necessary each structure to have...

...t; ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) > > Others imply a structure added to the end: > > #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) > > struct vfio_devtree_region_info_index > { > u32 index; > } > > #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) > > struct vfio_devtree_region_info_path > { > u32 len; > u8 path[]; > } > > The order of the flags indicates the order of the structures at the end. > We'd need to have some rules about alignment, probably always dword > ali...

...t; ?) > #define VFIO_DEVTREE_REGION_INFO_FLAG_RANGE (1 << ?) > > Others imply a structure added to the end: > > #define VFIO_DEVTREE_REGION_INFO_FLAG_INDEX (1 << ?) > > struct vfio_devtree_region_info_index > { > u32 index; > } > > #define VFIO_DEVTREE_REGION_INFO_FLAG_PATH (1 << ?) > > struct vfio_devtree_region_info_path > { > u32 len; > u8 path[]; > } > > The order of the flags indicates the order of the structures at the end. > We'd need to have some rules about alignment, probably always dword > ali...

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