From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/1] Monitor patches for 2019-11-19
Date: Tue, 19 Nov 2019 13:31:39 +0000 [thread overview]
Message-ID: <CAFEAcA-eY+61O4W=Sn0o9CSeszBn=LU=WHNvK8h_w3xtDWzp7Q@mail.gmail.com> (raw)
In-Reply-To: <20191119090037.21686-1-armbru@redhat.com>
On Tue, 19 Nov 2019 at 09:05, Markus Armbruster <armbru@redhat.com> wrote:
>
> I'd like to propose this bug fix for -rc2. Certain usage of QMP can
> leave the monitor permanently wedged (depends on event timing).
> Libvirt does not use it this way as far as I know. I understand it
> affects other applications. It's not a a regression in 4.2.
>
> If it's too late for fixing it in 4.2, we'll punt to 5.0 with cc:
> qemu-stable.
>
> The following changes since commit a5c2a235103ab366ad5318636ec138e52c6dcfa4:
>
> Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2019-11-18 17:06:17 +0000)
>
> are available in the Git repository at:
>
> git://repo.or.cz/qemu/armbru.git tags/pull-monitor-2019-11-19
>
> for you to fetch changes up to 2895aaa139b3f916b3650ca516b35dceb9c0d4c4:
>
> monitor/qmp: resume monitor when clearing its queue (2019-11-19 08:21:47 +0100)
>
> ----------------------------------------------------------------
> Monitor patches for 2019-11-19
>
> ----------------------------------------------------------------
> Wolfgang Bumiller (1):
> monitor/qmp: resume monitor when clearing its queue
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-11-19 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 9:00 [PULL 0/1] Monitor patches for 2019-11-19 Markus Armbruster
2019-11-19 9:00 ` [PULL 1/1] monitor/qmp: resume monitor when clearing its queue Markus Armbruster
2019-11-19 13:31 ` Peter Maydell [this message]
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='CAFEAcA-eY+61O4W=Sn0o9CSeszBn=LU=WHNvK8h_w3xtDWzp7Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=w.bumiller@proxmox.com \
/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).