Re: [libvirt] [PATCH v2] vhost-user: define conventions for vhost-user backends

> > It just reinvents the chardev unix socket syntax, but in a > > different adhoc manner, which is repeating the mistake we have > > made time & again in QEMU. Using QAPI we can directly accept > > the ChardevSocket syntax we already know about. Instead of > > having --socket-path and --fd and documenting that they are > > mutually exclusive ChardevSocket QAPI schema provides that > > representation in a well defined format which is discoverable > > and QEMU and mgmt apps already understand. > > That would require external vhost-user backends to implement QAPI/json > parsing. Is this necessary for a vhost-user backend? I doubt it. They could, but would not be required, to implement QAPI/json parser. The QAPI schema defines a standard for how to model & interpret the non-scalar values for command line arguments. An external impl would need to ensure that whatever parsing it does for CLI args is semantically compatible with the parsing rules defined by the QEMU QAPI schema we define to ensure interoperability of its impl.

Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|