[libvirt] summary of current vfio mdev upstreaming status
Daniel P. Berrange
berrange at redhat.com
Thu Sep 29 11:16:31 UTC 2016
On Thu, Sep 29, 2016 at 04:55:39PM +0800, Jike Song wrote:
> Hi all,
>
> In order to have a clear understanding about the VFIO mdev upstreaming
> status, I'd like to summarize it. Please share your opinions on this,
> and correct my misunderstandings.
>
> The whole vfio mdev series can be logically divided into several parts,
> they work together to provide the mdev support.
>
>
>
> PART 1: mdev core driver
>
> [task]
> - the mdev bus/device support
> - the utilities of mdev lifecycle management
> - the physical device register/unregister interfaces
>
> [status]
> - basically agreed by community
>
>
> PART 2: vfio bus driver for mdev
>
> [task]
> - interfaces with vendor drivers
> - the vfio bus implementation
>
> [status]
>
> - basically agreed by community
>
>
> PART 3: iommu support for mdev
>
> [task]
> - iommu support for mdev
>
> [status]
> - Kirti's v7 implementation, not yet fully reviewed
>
>
> PART 4: sysfs interfaces for mdev
>
> [task]
> - define the hierarchy of minimal sysfs directories/files
> - check the validity from vendor drivers, init/de-init them
> [status]
> - interfaces are in discussion
>
>
> PART 6: Documentation
>
> [task]
> - clearly document the architecture and interfaces
> - coding example for vendor drivers
>
> [status]
> - N/A
>
IMHO documentation should really be near the front as that's spelling out
the design. The implementation patches are then reviewed in reference to
the design documentation.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
More information about the libvir-list
mailing list