qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 7/7] chardev: add hotplug support.
Date: Fri, 12 Oct 2012 12:23:04 +0200	[thread overview]
Message-ID: <5077EF88.2070708@redhat.com> (raw)
In-Reply-To: <k58oib$n0$1@ger.gmane.org>

On 10/12/12 11:40, Paolo Bonzini wrote:
> Il 12/10/2012 11:26, Gerd Hoffmann ha scritto:
>> This patch adds chardev_add and chardev_del monitor commands.
>>
>> chardev_del is pretty straight forward, it just takes an id argument and
>> zaps the chardev specified.
>>
>> chardev_add is more tricky as there are tons of arguments for the
>> different backends.  The hmp version limited to the most common use
>> cases, especially when it comes to sockets:  You can only specify port
>> (tcp) or path (unix) and qemu will create a listening socket.  For
>> example this ...
>>
>>    (qemu) chardev_add foo socket 42
>>
>> ... will do the same as ...
>>
>>    -chardev socket,id=foo,port=42,server,nowait
> 
> Why not
> 
> chardev_add socket,id=foo,port=42,server,nowait
> 
> ?

Yea, maybe, but see below.

>> +{ 'command': 'chardev_add', 'data': {'id'      : 'str',
>> +                                     'backend' : 'str',
>> +                                     'path'    : 'str',
>> +                                     'name'    : 'str',
>> +                                     'host'    : 'str',
>> +                                     'port'    : 'str',
> 
> You cannot pass NULLs via QMP, so these need to be optional.

Fixed.

> I suggest that you implement the commands in a similar way as netdev_add.

Why?  Isn't the whole point of using josn is that you'll get the stuff
from the josn parser & marshaller in a usable form instead of having it
to feed into yet another parser?  I think the only reason netdev_add
exists in the current form is that it predates qmp.

cheers,
  Gerd

  reply	other threads:[~2012-10-12 10:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  9:25 [Qemu-devel] [PULL 0/7] serial device hotplug patch series Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 1/7] serial: split serial.c Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 2/7] serial: add pci variant Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 3/7] serial: add windows inf file for the pci card to docs Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 4/7] serial: add 2x + 4x pci variant Gerd Hoffmann
2012-10-12  9:26 ` [Qemu-devel] [PATCH 5/7] usb-serial: don't magically zap chardev on umplug Gerd Hoffmann
2012-10-12  9:26 ` [Qemu-devel] [PATCH 6/7] usb-serial: only expose device in guest when the chardev is open Gerd Hoffmann
2012-10-12  9:26 ` [Qemu-devel] [PATCH 7/7] chardev: add hotplug support Gerd Hoffmann
2012-10-12  9:40   ` Paolo Bonzini
2012-10-12 10:23     ` Gerd Hoffmann [this message]
2012-10-12 10:50       ` Paolo Bonzini
2012-10-12 11:15         ` Gerd Hoffmann
2012-10-12 11:17           ` Paolo Bonzini
2012-10-12 12:37             ` Gerd Hoffmann
2012-10-12 12:39               ` [Qemu-devel] [PATCH v2] " Gerd Hoffmann
2012-10-12 13:12                 ` Gerd Hoffmann
2012-10-12 16:54                 ` Paolo Bonzini
2012-10-12 17:08                   ` Paolo Bonzini
2012-10-15  6:51                 ` Lei Li
2012-10-15 11:09                   ` Andreas Färber
2012-10-16 13:23                     ` Luiz Capitulino
2012-10-15 17:36                   ` Eric Blake
2012-10-16 14:02                     ` Paolo Bonzini
2012-10-12  9:42 ` [Qemu-devel] [PULL 0/7] serial device hotplug patch series Paolo Bonzini

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=5077EF88.2070708@redhat.com \
    --to=kraxel@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).