Re: [libvirt] [PATCH v4 4/6] nodedev: Introduce the mdev capability to a PCI parent device

2017-05-18 Thread Erik Skultety
On Thu, May 18, 2017 at 06:48:48AM -0400, John Ferlan wrote: > [...] > > >>> +static int > >>> +udevFillMdevType(struct udev_device *device, > >>> + const char *dir, > >>> + virNodeDevCapMdevTypePtr type) > >>> +{ > >>> +int ret = -1; > >>> +char *attrpath =

Re: [libvirt] [PATCH v4 4/6] nodedev: Introduce the mdev capability to a PCI parent device

2017-05-18 Thread John Ferlan
[...] >>> +static int >>> +udevFillMdevType(struct udev_device *device, >>> + const char *dir, >>> + virNodeDevCapMdevTypePtr type) >>> +{ >>> +int ret = -1; >>> +char *attrpath = NULL; >>> + >>> +#define MDEV_GET_SYSFS_ATTR(attr_name, cb, ...)

Re: [libvirt] [PATCH v4 4/6] nodedev: Introduce the mdev capability to a PCI parent device

2017-05-18 Thread Erik Skultety
On Wed, May 17, 2017 at 05:22:45PM -0400, John Ferlan wrote: > > > On 05/15/2017 08:10 AM, Erik Skultety wrote: > > The parent device needs to report the generic stuff about the supported > > mediated devices types, like device API, available instances, type name, > > etc. Therefore this patch

Re: [libvirt] [PATCH v4 4/6] nodedev: Introduce the mdev capability to a PCI parent device

2017-05-17 Thread John Ferlan
On 05/15/2017 08:10 AM, Erik Skultety wrote: > The parent device needs to report the generic stuff about the supported > mediated devices types, like device API, available instances, type name, > etc. Therefore this patch introduces a new nested capability element of > type 'mdev_types' with the

[libvirt] [PATCH v4 4/6] nodedev: Introduce the mdev capability to a PCI parent device

2017-05-15 Thread Erik Skultety
The parent device needs to report the generic stuff about the supported mediated devices types, like device API, available instances, type name, etc. Therefore this patch introduces a new nested capability element of type 'mdev_types' with the resulting XML of the following format: ...