From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Victor Kaplansky" <victork@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
libvir-list@redhat.com, "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
Gonglei <arei.gonglei@huawei.com>,
"Felipe Franciosi" <felipe@nutanix.com>,
"Changpeng Liu" <changpeng.liu@intel.com>
Subject: Re: [Qemu-devel] [PATCH v2] vhost-user: define conventions for vhost-user backends
Date: Fri, 12 Oct 2018 11:28:23 +0100 [thread overview]
Message-ID: <20181012102823.GW16720@redhat.com> (raw)
In-Reply-To: <20181012102311.uojhijhdrbaxrjw3@sirius.home.kraxel.org>
On Fri, Oct 12, 2018 at 12:23:11PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > Note, I can't remember what Markus had proposed for CLI arguments in
> > QAPI, so I invented something arbitary but plausible.
>
> Using qapi visitors to parse the command line. Used by -blockdev and
> -display (and maybe others meanwhile). See parse_display_qapi().
>
> I think Daniels suggestion was to do that in the backends ...
More than just that - I was thinking of this series:
http://lists.gnu.org/archive/html/qemu-devel/2017-10/msg00209.html
In that there is no QemuOpts, or getopt(), etc. You end up using QAPI
for the entire argv parsing procss:
QAPIOption *qopt;
qopt = qapi_options_parse(argc, argv);
for (i = 0; !qopt[i].cnt; i++) {
switch (qopt[i].type) {
case QAPI_OPTION_KIND_NODEFCONFIG:
defconfig = false;
break;
case QAPI_OPTION_KIND_NO_USER_CONFIG:
userconfig = false;
break;
...etc...
}
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 :|
next prev parent reply other threads:[~2018-10-12 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 13:52 [Qemu-devel] [PATCH v2] vhost-user: define conventions for vhost-user backends Marc-André Lureau
2018-10-05 13:50 ` Ján Tomko
2018-10-05 14:23 ` Marc-André Lureau
2018-10-05 15:58 ` Hoffmann, Gerd
2018-10-05 22:32 ` Marc-André Lureau
2018-10-10 9:59 ` Hoffmann, Gerd
2018-10-11 15:48 ` Daniel P. Berrangé
2018-10-12 9:37 ` Daniel P. Berrangé
2018-10-12 10:23 ` Gerd Hoffmann
2018-10-12 10:28 ` Daniel P. Berrangé [this message]
2018-10-12 9:43 ` Marc-André Lureau
2018-10-12 9:55 ` Daniel P. Berrangé
2018-10-16 10:47 ` Marc-André Lureau
2018-10-16 12:14 ` Daniel P. Berrangé
2018-10-31 15:44 ` Marc-André Lureau
2018-10-31 16:04 ` Daniel P. Berrangé
2018-11-01 8:32 ` Marc-André Lureau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181012102823.GW16720@redhat.com \
--to=berrange@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=changpeng.liu@intel.com \
--cc=dgilbert@redhat.com \
--cc=felipe@nutanix.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=victork@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.