All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Michal Privoznik <mprivozn@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RfC 0/9] chardev hotplug
Date: Thu, 20 Dec 2012 12:45:33 +0100	[thread overview]
Message-ID: <50D2FA5D.30602@redhat.com> (raw)
In-Reply-To: <50D2F23D.9000908@redhat.com>

>>>> I doubt I manage to finish (and test!) it before xmas.
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
>>> 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?
> 
> I think that is the missing part.

Exactly.

/me wades through the socket code (unix+tcp) right now, which needs some
refactoring to make it fly.

>> From libvirt's POV, I think the most important chardev types are pty,
>> unix and tcp. The other types are pretty rarely used AFAICT.

pty looks like another non-trivial challenge.  How does libvirt gather
the pty device today?  IIRC there is some stderr parsing?  Or was it
info chardev?  With QMP we probably want switch to a more sane model
here ...

cheers,
  Gerd

  reply	other threads:[~2012-12-20 11:45 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 ` [Qemu-devel] [PATCH RfC 0/9] chardev hotplug Michal Privoznik
2012-12-20 10:56   ` Daniel P. Berrange
2012-12-20 11:10     ` Paolo Bonzini
2012-12-20 11:45       ` Gerd Hoffmann [this message]
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=50D2FA5D.30602@redhat.com \
    --to=kraxel@redhat.com \
    --cc=mprivozn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.