From: Michal Privoznik <mprivozn@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RfC 0/9] chardev hotplug
Date: Thu, 20 Dec 2012 11:49:29 +0100 [thread overview]
Message-ID: <50D2ED39.6010608@redhat.com> (raw)
In-Reply-To: <1355932747-1755-1-git-send-email-kraxel@redhat.com>
On 19.12.2012 16:58, Gerd Hoffmann wrote:
> Hi,
>
> Chardev hotplug patch series reloaded. Not finished yet, commit
> messages not finalized yet, totally untested other than building on
> linux+windows.
>
> I doubt I manage to finish (and test!) it before xmas. Nevertheless I
> wanna get the bits out of the door for you to see what is coming and for
> early reviews. It goes largely the route suggested by Paolo.
>
> cheers,
> Gerd
>
> Gerd Hoffmann (9):
> chardev: add error reporting for qemu_chr_new_from_opts
> chardev: fix QemuOpts lifecycle
> chardev: reduce chardev ifdef mess a bit
> chardev: hotplug, qmp, null
> chardev: hotplug, hmp
> chardev: hotplug, qmp, file
> chardev: hotplug, qmp, tty
> chardev: hotplug, qmp, serial
> chardev: hotplug, qmp, parallel
>
> hmp-commands.hx | 32 ++++++
> hmp.c | 23 +++++
> hmp.h | 2 +
> qapi-schema.json | 47 +++++++++
> qemu-char.c | 280 ++++++++++++++++++++++++++++++++++++++++++++---------
> qemu-char.h | 4 +-
> qmp-commands.hx | 50 ++++++++++
> vl.c | 9 +-
> 8 files changed, 395 insertions(+), 52 deletions(-)
>
Okay, the QMP interface seems sane to me (from libvirt POV). However,
what about other chardev types like pipe and vc? And I guess pty can be
covered by tty, right?
Michal
next prev parent reply other threads:[~2012-12-20 10:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 15:58 [Qemu-devel] [PATCH RfC 0/9] chardev hotplug Gerd Hoffmann
2012-12-19 15:58 ` [Qemu-devel] [PATCH 1/9] chardev: add error reporting for qemu_chr_new_from_opts Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 2/9] chardev: fix QemuOpts lifecycle Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 3/9] chardev: reduce chardev ifdef mess a bit Gerd Hoffmann
2012-12-19 20:04 ` Blue Swirl
2012-12-19 15:59 ` [Qemu-devel] [PATCH 4/9] chardev: hotplug, qmp, null Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 5/9] chardev: hotplug, hmp Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 6/9] chardev: hotplug, qmp, file Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 7/9] chardev: hotplug, qmp, tty Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 8/9] chardev: hotplug, qmp, serial Gerd Hoffmann
2012-12-19 16:21 ` Paolo Bonzini
2012-12-20 7:09 ` Gerd Hoffmann
2012-12-19 15:59 ` [Qemu-devel] [PATCH 9/9] chardev: hotplug, qmp, parallel Gerd Hoffmann
2012-12-20 10:49 ` Michal Privoznik [this message]
2012-12-20 10:56 ` [Qemu-devel] [PATCH RfC 0/9] chardev hotplug Daniel P. Berrange
2012-12-20 11:10 ` Paolo Bonzini
2012-12-20 11:45 ` Gerd Hoffmann
2012-12-20 13:02 ` Gerd Hoffmann
2012-12-21 11:45 ` Gerd Hoffmann
2012-12-21 11:53 ` Paolo Bonzini
2012-12-21 12:17 ` Gerd Hoffmann
2012-12-21 12:40 ` Paolo Bonzini
2012-12-21 14:21 ` Gerd Hoffmann
2012-12-20 16:44 ` Daniel P. Berrange
2012-12-21 9:01 ` Gerd Hoffmann
2012-12-21 9:28 ` Daniel P. Berrange
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=50D2ED39.6010608@redhat.com \
--to=mprivozn@redhat.com \
--cc=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).