search for: smarduch

Displaying 4 results from an estimated 4 matches for "smarduch".

2013 Jul 04
0
RFC: vfio interface for platform devices (v2)
On 04.07.2013, at 16:44, Mario Smarduch wrote: > > I'm having trouble understanding how this works where > the Guest Device Model != Host. How do you inform the guest > where the device is mapped in its physical address space, > and handle GPA faults? The same way as you would for emulated devices. Alex
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
Version 2 -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, defined 5 new flags and associated structs -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, defined 1 new flag and
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
Version 2 -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, defined 5 new flags and associated structs -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, defined 1 new flag and
2013 Jul 04
0
RFC: vfio interface for platform devices (v2)
I'm having trouble understanding how this works where the Guest Device Model != Host. How do you inform the guest where the device is mapped in its physical address space, and handle GPA faults? - Mario On 7/3/2013 11:40 PM, Yoder Stuart-B08248 wrote: > Version 2 > -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path > -VFIO_DEVICE_GET_INFO-- defined 2 flags