Re: [libvirt] [PATCH 2/2] Introduce DOMAIN_DEVICE_ITERATE_MISSING_INFO

2019-05-23 Thread Ján Tomko
On Wed, May 22, 2019 at 05:22:42PM +0200, Andrea Bolognani wrote: On Tue, 2019-05-21 at 16:26 +0200, Ján Tomko wrote: Rename the DOMAIN_DEVICE_ITERATE_GRAPHICS flag. It was introduced by commit dd45c2710f6fd2d4f8a47f97960532d0e0091e7d with the intention to run the Validate callback even on the g

Re: [libvirt] [PATCH 2/2] Introduce DOMAIN_DEVICE_ITERATE_MISSING_INFO

2019-05-22 Thread Andrea Bolognani
On Tue, 2019-05-21 at 16:26 +0200, Ján Tomko wrote: > Rename the DOMAIN_DEVICE_ITERATE_GRAPHICS flag. > It was introduced by commit dd45c2710f6fd2d4f8a47f97960532d0e0091e7d > with the intention to run the Validate callback even on the graphics > device. > > However, enumerating every single device

[libvirt] [PATCH 2/2] Introduce DOMAIN_DEVICE_ITERATE_MISSING_INFO

2019-05-21 Thread Ján Tomko
Rename the DOMAIN_DEVICE_ITERATE_GRAPHICS flag. It was introduced by commit dd45c2710f6fd2d4f8a47f97960532d0e0091e7d with the intention to run the Validate callback even on the graphics device. However, enumerating every single device in virDomainDeviceIterateFlags is unsustainable and what really