qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] char: report frontend open/closed state in 'query-chardev'
Date: Wed, 25 Jun 2014 09:02:00 -0400	[thread overview]
Message-ID: <20140625090200.693e6999@redhat.com> (raw)
In-Reply-To: <53A98CF4.9090302@redhat.com>

On Tue, 24 Jun 2014 08:36:36 -0600
Eric Blake <eblake@redhat.com> wrote:

> [cc'ing Luiz]
> 
> On 06/24/2014 08:21 AM, Laszlo Ersek wrote:
> > On 05/29/14 23:05, Eric Blake wrote:
> >> On 05/29/2014 02:43 PM, Laszlo Ersek wrote:
> 
> >>> In this series I try to implement the ideas that (I believe) were
> >>> suggested by Gerd and Amit in
> >>> <https://bugzilla.redhat.com/show_bug.cgi?id=1080376>.
> >>> 
> >>> When the guest agent exits or dies (disconnects from the virtio-serial
> >>> port), the backend (eg. a host-side unix domain socket) doesn't (in
> >>> general, can't) reflect it. This lack of info tends to trip up libvirt
> >>> in some cases, waiting indefinitely for an agent that doesn't exist.
> >>> 
> >>> The series adds two monitor events that report about virtio-serial ports
> >>> being opened and closed (for online notification), and extends the
> >>> "query-chardev" QMP command's return type with a "frontend_open" bool
> >>> (for querying at late libvirt startup).
> 
> >>
> >>>>> +#                 backend (eg. with the chardev=... option) is in open or
> >>>>> +#                 closed state (since 2.2)
> >>>>
> >>>> Why 2.2? Are you saying it is too late to make the 2.1 soft freeze?
> >>>
> >>> I thought that reviewers would immediately question the direction of the
> >>> patchset (ie. monitor events + new query field), and not just suggest
> >>> tweaks; so 2.2 seemed safer. Perhaps I can make it till the 2.1 soft
> >>> freeze (June 17th), but that depends (as I've learned now) on Wenchao's
> >>> series too.
> >>
> >> Actually, I think your series and Wenchao's are mostly orthogonal -
> >> either could go in first, and it's just fine if one hits 2.1 while the
> >> other waits till 2.2.  It's just a matter of code churn, where getting
> >> both in means whoever is second has to consider the code added in the
> >> meantime (either your series is tweaked to use the qapi generation, or
> >> Wenchao's series is tweaked to convert "one" more event).
> > 
> > I'm thinking about resuming work on this. Wenchao's series has been
> > applied (ends at commit 75175173). We're between soft and hard freeze
> > now. Should I aim at 2.1 or 2.2?
> 
> This series was posted before soft freeze, but adds a new feature.  If
> we're going to get it in the 2.1 release, it must be before hard freeze.
>  I'll leave it up to Luiz whether a QMP addition this late in the game
> is safe to take, although my personal opinion is that since it was
> proposed before soft freeze, and DOES make life easier for libvirt, it
> is worth a strong consideration.

Has this series being reviewed?

  reply	other threads:[~2014-06-25 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1401392201-29988-1-git-send-email-lersek@redhat.com>
2014-06-06  9:43 ` [Qemu-devel] [PATCH 0/2] help libvirt know what's up with qga Amit Shah
     [not found] ` <1401392201-29988-3-git-send-email-lersek@redhat.com>
     [not found]   ` <538794A9.1000906@redhat.com>
     [not found]     ` <53879BDB.8050403@redhat.com>
     [not found]       ` <5387A118.5090304@redhat.com>
2014-06-24 14:21         ` [Qemu-devel] [PATCH 2/2] char: report frontend open/closed state in 'query-chardev' Laszlo Ersek
2014-06-24 14:36           ` Eric Blake
2014-06-25 13:02             ` Luiz Capitulino [this message]
2014-06-25 13:14               ` Eric Blake
2014-06-25 13:16                 ` Luiz Capitulino
2014-06-25 13:25                   ` Laszlo Ersek
2014-06-25 13:30                     ` Luiz Capitulino

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=20140625090200.693e6999@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lersek@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).