qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com
Subject: [Qemu-devel] [RFC 0/3] monitor: allow per-monitor events
Date: Wed,  4 Jul 2018 17:10:35 +0800	[thread overview]
Message-ID: <20180704091038.29449-1-peterx@redhat.com> (raw)

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.

Thanks,

Peter Xu (3):
  monitor: allow monitor_qapi_event_emit specify mon
  monitor: let QMPEventFuncEmit take a monitor arg
  qapi: provide send/bcast interface for events

 include/qapi/qmp-event.h   |  6 +++-
 block/block-backend.c      |  6 ++--
 block/qcow2.c              |  2 +-
 block/quorum.c             |  4 +--
 block/write-threshold.c    |  2 +-
 blockjob.c                 | 10 +++---
 cpus.c                     |  8 ++---
 dump.c                     |  2 +-
 hw/acpi/core.c             |  2 +-
 hw/acpi/cpu.c              |  2 +-
 hw/acpi/memory_hotplug.c   |  4 +--
 hw/char/virtio-console.c   |  2 +-
 hw/core/qdev.c             |  2 +-
 hw/net/virtio-net.c        |  2 +-
 hw/ppc/spapr_rtc.c         |  2 +-
 hw/timer/mc146818rtc.c     |  2 +-
 hw/virtio/virtio-balloon.c |  2 +-
 hw/watchdog/watchdog.c     | 14 ++++-----
 job.c                      |  2 +-
 migration/migration.c      |  4 +--
 migration/ram.c            |  2 +-
 monitor.c                  | 62 +++++++++++++++++++++++++++++---------
 scsi/pr-manager-helper.c   |  2 +-
 tests/test-qmp-event.c     | 10 +++---
 ui/spice-core.c            |  8 ++---
 ui/vnc.c                   |  6 ++--
 vl.c                       | 14 ++++-----
 scripts/qapi/common.py     | 16 ++++++++--
 scripts/qapi/events.py     | 27 ++++++++++++-----
 trace-events               |  2 +-
 30 files changed, 146 insertions(+), 83 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-07-04  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  9:10 Peter Xu [this message]
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 ` [Qemu-devel] [RFC 0/3] monitor: allow per-monitor events Peter Xu

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=20180704091038.29449-1-peterx@redhat.com \
    --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).