From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 0/3] monitor: allow per-monitor events
Date: Wed, 4 Jul 2018 17:19:31 +0800 [thread overview]
Message-ID: <20180704091931.GC2568@xz-mi> (raw)
In-Reply-To: <20180704091038.29449-1-peterx@redhat.com>
On Wed, Jul 04, 2018 at 05:10:35PM +0800, Peter Xu wrote:
> This series tries to allow QEMU to send events to specific monitor.
> Markus told me to send this out before I threw the code away, so I
> did. Testing only covered compilation and qtest to make sure the
> broadcast way should be working at least.
>
> No real user, no nice testing, no idea on whether it could finally be
> used - it takes the RFC tag then.
This is based on below series:
Subject: [PATCH 0/9] monitor: enable OOB by default
Patchew version:
Based-on: <20180704084507.14560-1-peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2018-07-04 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 9:10 [Qemu-devel] [RFC 0/3] monitor: allow per-monitor events Peter Xu
2018-07-04 9:10 ` [Qemu-devel] [RFC 1/3] monitor: allow monitor_qapi_event_emit specify mon Peter Xu
2018-07-04 9:10 ` [Qemu-devel] [RFC 2/3] monitor: let QMPEventFuncEmit take a monitor arg Peter Xu
2018-07-04 9:10 ` [Qemu-devel] [RFC 3/3] qapi: provide send/bcast interface for events Peter Xu
2018-07-04 9:19 ` Peter Xu [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=20180704091931.GC2568@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@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).