search for: device_get_info

...d be > discussing them separately. We do need to keep core resources separate from what it takes to generate a guest DT, but note the purpose of the devtree info is not primarily to help generate a guest DT. User space (not just QEMU) needs to know what the regions and interrupts advertised by DEVICE_GET_INFO correspond to. If there are 4 interrupts and 2 register regions, how does user space know the purpose/function of each? Apart from something like the devtree info I don't see how a user space driver can know how to use the regions and interrupts. The kernel is not guaranteeing any particular...

...> >> fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); >> >> (whether the path is a device tree path or a sysfs path is up for >> discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") >> >> 2. VFIO_DEVICE_GET_INFO >> >> Don't think any changes are needed to VFIO_DEVICE_GET_INFO other >> than adding a new flag identifying a devices as a 'platform' >> device. >> >> This ioctl simply returns the number of regions and number of irqs. >> >>...

...> >> fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); >> >> (whether the path is a device tree path or a sysfs path is up for >> discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") >> >> 2. VFIO_DEVICE_GET_INFO >> >> Don't think any changes are needed to VFIO_DEVICE_GET_INFO other >> than adding a new flag identifying a devices as a 'platform' >> device. >> >> This ioctl simply returns the number of regions and number of irqs. >> >>...

...device information: > > fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); > > (whether the path is a device tree path or a sysfs path is up for > discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") > > 2. VFIO_DEVICE_GET_INFO > > Don't think any changes are needed to VFIO_DEVICE_GET_INFO other > than adding a new flag identifying a devices as a 'platform' > device. > > This ioctl simply returns the number of regions and number of irqs. > > The number of regions corre...

...c platform device path to get the device information: fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); (whether the path is a device tree path or a sysfs path is up for discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") 2. VFIO_DEVICE_GET_INFO Don't think any changes are needed to VFIO_DEVICE_GET_INFO other than adding a new flag identifying a devices as a 'platform' device. This ioctl simply returns the number of regions and number of irqs. The number of regions corresponds to the number of regions that...

...c platform device path to get the device information: fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/soc at ffe000000/usb at 210000"); (whether the path is a device tree path or a sysfs path is up for discussion, e.g. "/sys/bus/platform/devices/ffe210000.usb") 2. VFIO_DEVICE_GET_INFO Don't think any changes are needed to VFIO_DEVICE_GET_INFO other than adding a new flag identifying a devices as a 'platform' device. This ioctl simply returns the number of regions and number of irqs. The number of regions corresponds to the number of regions that...