qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrangé" <berrange@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 12:23:11 +0200	[thread overview]
Message-ID: <20181012102311.uojhijhdrbaxrjw3@sirius.home.kraxel.org> (raw)
In-Reply-To: <20181012093757.GT16720@redhat.com>

  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 ...

cheers,
  Gerd

  reply	other threads:[~2018-10-12 10:23 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 [this message]
2018-10-12 10:28       ` Daniel P. Berrangé
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=20181012102311.uojhijhdrbaxrjw3@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=changpeng.liu@intel.com \
    --cc=dgilbert@redhat.com \
    --cc=felipe@nutanix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).