From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 01/12] monitor: use monitor_handle_fd_param for non-Error-friendly users of named fds
Date: Thu, 20 Sep 2012 10:47:18 -0300 [thread overview]
Message-ID: <20120920104718.018c16b5@doriath.home> (raw)
In-Reply-To: <505ACF52.7090108@redhat.com>
On Thu, 20 Sep 2012 10:09:54 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 19/09/2012 22:42, Luiz Capitulino ha scritto:
> > On Wed, 19 Sep 2012 16:31:04 +0200
> > Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >> monitor_handle_fd_param and monitor_get_fd are mostly the same, except
> >> that monitor_handle_fd_param does error reporting wrong. Use it in all
> >> other places that do it wrong, instead of reinventing it.
> >
> > Hmm, why do we want to do this?
> >
> > As far as I understand it the main difference between the two functions
> > is that if fdname is a number (for a weak definition of number),
> > monitor_handle_fd_param() assumes that the fd already exists in qemu
> > (eg. it was passed by the parent process).
>
> Oops, right, I remembered it was the other way round (i.e. first search
> for a named file descriptor, and fall back to a numeric one).
That's a lot better, IMO.
> > Another side effect is that you add the possibility of functions
> > changing from monitor_get_fd() to monitor_handle_fd_param() to also take
> > fds passed by the parent process. Might be positive, but I wonder if that's
> > useful for the commands you're changing.
>
> Making behavior more uniform may be a useful thing on its own. We might
> even consider moving it to monitor_get_fd (with the above tweak for
> compatibility).
Yes, although I can think of another issue: suppose an mngt app passes an
fd with fdname=9, but the fd doesn't reach qemu for some reason. Then the
mngt app executes a qmp command with fdname=9 and fd 9 turns out to exist
in qemu... Actually, a mngt app could do this even w/o passing an fd to
qemu.
Not sure how relevant this issue is though, as this can happen today
with qmp commands using monitor_handle_fd_param().
> BTW, pci-assign.c is open-coding
> monitor_handle_fd_param (including the numeric file descriptor behavior)
> and we can remove the surrounding if.
Yes, that's fine.
next prev parent reply other threads:[~2012-09-20 13:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 14:31 [Qemu-devel] [PATCH 00/12] QAPI prerequisites for the embedded NBD server Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 01/12] monitor: use monitor_handle_fd_param for non-Error-friendly users of named fds Paolo Bonzini
2012-09-19 20:42 ` Luiz Capitulino
2012-09-20 8:09 ` Paolo Bonzini
2012-09-20 13:47 ` Luiz Capitulino [this message]
2012-09-20 14:33 ` Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 02/12] monitor: add Error * argument to monitor_get_fd Paolo Bonzini
2012-09-19 20:47 ` Luiz Capitulino
2012-09-19 14:31 ` [Qemu-devel] [PATCH 03/12] qapi: do not protect enum values from namespace pollution Paolo Bonzini
2012-09-20 14:07 ` Luiz Capitulino
2012-09-19 14:31 ` [Qemu-devel] [PATCH 04/12] qapi: add "unix" to the set of reserved words Paolo Bonzini
2012-09-19 15:46 ` Peter Maydell
2012-09-19 15:58 ` Paolo Bonzini
2012-09-19 16:02 ` Paolo Bonzini
2012-09-19 19:29 ` Blue Swirl
2012-09-20 14:08 ` Luiz Capitulino
2012-09-19 14:31 ` [Qemu-devel] [PATCH 05/12] build: add QAPI files to the tools Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 06/12] qapi: add socket address types Paolo Bonzini
2012-09-19 17:20 ` Eric Blake
2012-09-20 8:01 ` Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 07/12] qemu-sockets: add error propagation to inet_parse Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 08/12] qemu-sockets: add error propagation to Unix socket functions Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 09/12] qemu-sockets: return IPSocketAddress from inet_parse Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 10/12] qemu-sockets: move block from QemuOpts to arguments Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 11/12] qemu-sockets: add block and in_progress arguments to unix_connect_opts Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 12/12] qemu-sockets: add socket_listen, socket_connect, socket_parse Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 13/12] block: add close notifiers Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 14/12] qmp: add NBD server commands Paolo Bonzini
2012-09-19 17:48 ` Eric Blake
2012-09-20 8:01 ` Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 15/12] hmp: " Paolo Bonzini
2012-09-19 18:02 ` Eric Blake
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=20120920104718.018c16b5@doriath.home \
--to=lcapitulino@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).