qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 7/9] sockets: allow SocketAddress 'fd' to reference numeric file descriptors
Date: Mon, 12 Mar 2018 12:44:46 +0000	[thread overview]
Message-ID: <20180312124446.GA8576@redhat.com> (raw)
In-Reply-To: <6f0d724e-3275-6700-d41d-8f378de8835b@redhat.com>

On Tue, Feb 06, 2018 at 08:48:43AM -0600, Eric Blake wrote:
> On 02/06/2018 03:13 AM, Daniel P. Berrangé wrote:
> 
> > > > +++ b/qapi/sockets.json
> > > > @@ -123,6 +123,13 @@
> > > >    #
> > > >    # @unix:  Unix domain socket
> > > >    #
> > > > +# @vsock: VMCI address
> > > > +#
> > > > +# @fd: decimal is for file descriptor number, otherwise a file descriptor name.
> > > > +#      Named file descriptors are permitted in monitor commands, in combination
> > > > +#      with the 'getfd' command. Decimal file descriptors are permitted at
> > > > +#      startup or other contexts where no monitor context is active.
> > > > +#
> > > >    # Since: 2.9
> > > 
> > > There doesn't seem to be any way to introspect if we support decimal fds
> > > from the command line; is that going to be a problem?
> > 
> > Libvirt needs to know when it can use it, so any suggestions ?
> 
> Patch 9/9 modified qemu_chardev_opts; does that change reflect through
> query-command-line-options?  Not all QemuOpts changes are introspectible
> yet, and Markus has been trying to tackle that, but if this particular one
> works, we can use that as our witness (after all, if I understand correctly,
> the new feature you are adding here is NOT affecting the QMP usage, but is
> an enhancement for command-line usage).

Yeah, 'fd' does appear there, so that's good enough for now.

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

  reply	other threads:[~2018-03-12 12:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 15:24 [Qemu-devel] [PATCH v4 0/9] Enable passing pre-opened chardev socket FD Daniel P. Berrangé
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 1/9] char: don't silently skip tn3270 protocol init when TLS is enabled Daniel P. Berrangé
2018-02-05 16:10   ` Cornelia Huck
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 2/9] cutils: add qemu_strtoi & qemu_strtoui parsers for int/unsigned int types Daniel P. Berrangé
2018-02-05 19:37   ` Eric Blake
2018-02-07 16:29     ` Daniel P. Berrangé
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 3/9] sockets: pull code for testing IP availability out of specific test Daniel P. Berrangé
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 4/9] sockets: strengthen test suite IP protocol availability checks Daniel P. Berrangé
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 5/9] sockets: move fd_is_socket() into common sockets code Daniel P. Berrangé
2018-02-05 16:13   ` Marc-Andre Lureau
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 6/9] sockets: check that the named file descriptor is a socket Daniel P. Berrangé
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 7/9] sockets: allow SocketAddress 'fd' to reference numeric file descriptors Daniel P. Berrangé
2018-02-05 19:42   ` Eric Blake
2018-02-06  9:13     ` Daniel P. Berrangé
2018-02-06 14:48       ` Eric Blake
2018-03-12 12:44         ` Daniel P. Berrangé [this message]
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 8/9] char: refactor parsing of socket address information Daniel P. Berrangé
2018-02-05 15:24 ` [Qemu-devel] [PATCH v4 9/9] char: allow passing pre-opened socket file descriptor at startup Daniel P. Berrangé
2018-02-05 17:33 ` [Qemu-devel] [PATCH v4 0/9] Enable passing pre-opened chardev socket FD no-reply

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=20180312124446.GA8576@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).