search for: ffe210000

...should be a way > for root to tell vfio that a device is allowed to overmap, in order to > get the performance benefit of direct access in cases where root knows > (or explicitly doesn't care) that it is safe. Perhaps a sysfs mechanism like this: echo "/sys/bus/platform/devices/ffe210000.usb" > /sys/bus/platform/drivers/vfio-platform/allow_overmap Stuart

On 07/02/2013 08:07:53 PM, Alexander Graf wrote: > > On 03.07.2013, at 01:25, Yoder Stuart-B08248 wrote: > > > 8. Open Issues > > > > -how to handle cases where VFIO is requested to handle > > a device where the valid, mappable range for a region > > is less than a page size. See example above where an > > advertised region in the DMA

On 07/02/2013 08:07:53 PM, Alexander Graf wrote: > > On 03.07.2013, at 01:25, Yoder Stuart-B08248 wrote: > > > 8. Open Issues > > > > -how to handle cases where VFIO is requested to handle > > a device where the valid, mappable range for a region > > is less than a page size. See example above where an > > advertised region in the DMA

...GET_DEVICE_FD passing a specific 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 correspo...

...GET_DEVICE_FD passing a specific 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 correspo...

...fd. 1. VFIO_GROUP_GET_DEVICE_FD User space knows by out-of-band means which device it is accessing and will call VFIO_GROUP_GET_DEVICE_FD passing a specific sysfs path to get the device information: fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/sys/bus/platform/devices/ffe210000.usb")); 2. VFIO_DEVICE_GET_INFO The number of regions corresponds to the regions defined in "reg" and "ranges" in the device tree. Two new flags are added to struct vfio_device_info: #define VFIO_DEVICE_FLAGS_PLATFORM (1 << ?) /* A platform bus devi...

...fd. 1. VFIO_GROUP_GET_DEVICE_FD User space knows by out-of-band means which device it is accessing and will call VFIO_GROUP_GET_DEVICE_FD passing a specific sysfs path to get the device information: fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, "/sys/bus/platform/devices/ffe210000.usb")); 2. VFIO_DEVICE_GET_INFO The number of regions corresponds to the regions defined in "reg" and "ranges" in the device tree. Two new flags are added to struct vfio_device_info: #define VFIO_DEVICE_FLAGS_PLATFORM (1 << ?) /* A platform bus devi...

...form 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") Doesn't VFIO need to operate on an actual Linux device, rather than just an OF node? Are we going to have a fixed assumption that you always want all the children of the node corresponding to the assigned device, or will it be possible to exclude some? > 2. VFIO_DEVICE_G...

...gt; > User space knows by out-of-band means which device it is accessing > and will call VFIO_GROUP_GET_DEVICE_FD passing a specific sysfs path > to get the device information: > > fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, > "/sys/bus/platform/devices/ffe210000.usb")); > > 2. VFIO_DEVICE_GET_INFO > > The number of regions corresponds to the regions defined > in "reg" and "ranges" in the device tree. > > Two new flags are added to struct vfio_device_info: > > #define VFIO_DEVICE_FLAGS_P...

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

...gt; > User space knows by out-of-band means which device it is accessing > and will call VFIO_GROUP_GET_DEVICE_FD passing a specific sysfs path > to get the device information: > > fd = ioctl(group, VFIO_GROUP_GET_DEVICE_FD, > "/sys/bus/platform/devices/ffe210000.usb")); FWIW, I'm in favor of whichever way works out cleaner in the code for pre-pending "/sys/bus" or not. It sort of seems like it's unnecessary. It's also a little inconsistent that the returned path doesn't pre-pend /sys in the examples below. > 2. VFIO_DE...

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

...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") > > Doesn't VFIO need to operate on an actual Linux device, rather than > just an OF node? > > Are we going to have a fixed assumption that you always want all the > children of the node corresponding to the assigned device, or will it > be possible to exclude...

...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") > > Doesn't VFIO need to operate on an actual Linux device, rather than > just an OF node? > > Are we going to have a fixed assumption that you always want all the > children of the node corresponding to the assigned device, or will it > be possible to exclude...

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

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