search for: vfio_path_info

...multiple sub-regions per "reg" or "ranges" and > > the sub-index within the reg/ranges is needed > > > > The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. > > > > ioctl: VFIO_DEVICE_GET_DEVTREE_INFO > > > > struct vfio_path_info { > > __u32 argsz; > > __u32 flags; > > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a > > "ranges" property */ > > What about distinguishing a normal interrupt from one found in an > interrupt-map? I'm...

...multiple sub-regions per "reg" or "ranges" and > > the sub-index within the reg/ranges is needed > > > > The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. > > > > ioctl: VFIO_DEVICE_GET_DEVTREE_INFO > > > > struct vfio_path_info { > > __u32 argsz; > > __u32 flags; > > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a > > "ranges" property */ > > What about distinguishing a normal interrupt from one found in an > interrupt-map? I'm...

...g, 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. As long as we can be sure all architectures will map things correctly without any flags needing to be specified, that's fine. > > > struct vfio_path_info { > > > __u32 argsz; > > > __u32 flags; > > > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region > is a > > > "ranges" property */ > > > > What about distinguishing a normal interrupt from one foun...

...ot; or "ranges" property -there could be multiple sub-regions per "reg" or "ranges" and the sub-index within the reg/ranges is needed The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. ioctl: VFIO_DEVICE_GET_DEVTREE_INFO struct vfio_path_info { __u32 argsz; __u32 flags; #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a "ranges" property */ __u32 index; /* input: index of region or irq for which we are getting info */ __u32 type; /* input: 0 - g...

...ot; or "ranges" property -there could be multiple sub-regions per "reg" or "ranges" and the sub-index within the reg/ranges is needed The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. ioctl: VFIO_DEVICE_GET_DEVTREE_INFO struct vfio_path_info { __u32 argsz; __u32 flags; #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a "ranges" property */ __u32 index; /* input: index of region or irq for which we are getting info */ __u32 type; /* input: 0 - g...

...erty > -there could be multiple sub-regions per "reg" or "ranges" and > the sub-index within the reg/ranges is needed > > The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. > > ioctl: VFIO_DEVICE_GET_DEVTREE_INFO > > struct vfio_path_info { > __u32 argsz; > __u32 flags; > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a > "ranges" property */ What about distinguishing a normal interrupt from one found in an interrupt-map? In the case of both ranges and interru...

...son to keep it? Will it > > help any decision that user space makes? Maybe we should just > > drop it. > > As long as we can be sure all architectures will map things correctly > without any flags needing to be specified, that's fine. > > > > > struct vfio_path_info { > > > > __u32 argsz; > > > > __u32 flags; > > > > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region > > is a > > > > "ranges" property */ > > > > > > What about distinguishing...

...son to keep it? Will it > > help any decision that user space makes? Maybe we should just > > drop it. > > As long as we can be sure all architectures will map things correctly > without any flags needing to be specified, that's fine. > > > > > struct vfio_path_info { > > > > __u32 argsz; > > > > __u32 flags; > > > > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region > > is a > > > > "ranges" property */ > > > > > > What about distinguishing...

...property > -there could be multiple sub-regions per "reg" or "ranges" and > the sub-index within the reg/ranges is needed > > The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. > > ioctl: VFIO_DEVICE_GET_DEVTREE_INFO > > struct vfio_path_info { > __u32 argsz; > __u32 flags; > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a "ranges" property */ > __u32 index; /* input: index of region or irq for which we are getting info */ > __u32 type;...

...y > -there could be multiple sub-regions per "reg" or "ranges" and > the sub-index within the reg/ranges is needed > > The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. > > ioctl: VFIO_DEVICE_GET_DEVTREE_INFO > > struct vfio_path_info { > __u32 argsz; > __u32 flags; > #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a "ranges" property */ (1 << 0)? Having flags = 0x0 for regs and 0x1 for ranges is a bit awkward. I'd suggest a bit for each. Otherwise, wh...

...uld be multiple sub-regions per "reg" or "ranges" and >> the sub-index within the reg/ranges is needed >> >> The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. >> >> ioctl: VFIO_DEVICE_GET_DEVTREE_INFO >> >> struct vfio_path_info { >> __u32 argsz; >> __u32 flags; >> #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a "ranges" property */ > > (1 << 0)? > > Having flags = 0x0 for regs and 0x1 for ranges is a bit awkward. I'd > sug...

...uld be multiple sub-regions per "reg" or "ranges" and >> the sub-index within the reg/ranges is needed >> >> The VFIO_DEVICE_GET_DEVTREE_INFO operates on a device fd. >> >> ioctl: VFIO_DEVICE_GET_DEVTREE_INFO >> >> struct vfio_path_info { >> __u32 argsz; >> __u32 flags; >> #define VFIO_DEVTREE_INFO_RANGES (1 << 3) /* the region is a "ranges" property */ > > (1 << 0)? > > Having flags = 0x0 for regs and 0x1 for ranges is a bit awkward. I'd > sug...