All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, armbru@redhat.com,
	stefanha@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/6] qapi: move event defines to qapi-schema.json
Date: Mon, 21 Oct 2013 21:45:54 +0100	[thread overview]
Message-ID: <52659282.3050004@redhat.com> (raw)
In-Reply-To: <1382321765-29052-5-git-send-email-xiawenc@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2360 bytes --]

On 10/21/2013 03:16 AM, Wenchao Xia wrote:
> They are defined with capitals for compatibility, see monitor_event_names
> in monitor.c, which was used to set the event strings.

Agree; the existing 'query-events' commands returns all-capital strings.

> 
> Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
> ---
>  include/monitor/monitor.h |   37 -------------------------------------
>  qapi-schema.json          |   37 +++++++++++++++++++++++++++++++++++++
>  2 files changed, 37 insertions(+), 37 deletions(-)
> 
> -typedef enum QEvent {
> -    Q_EVENT_SHUTDOWN,
> -    Q_EVENT_RESET,
> -    Q_EVENT_POWERDOWN,
> -    Q_EVENT_STOP,
> -    Q_EVENT_RESUME,
> -    Q_EVENT_VNC_CONNECTED,
> -    Q_EVENT_VNC_INITIALIZED,
> -    Q_EVENT_VNC_DISCONNECTED,
> -    Q_EVENT_BLOCK_IO_ERROR,
> -    Q_EVENT_RTC_CHANGE,
> -    Q_EVENT_WATCHDOG,
> -    Q_EVENT_SPICE_CONNECTED,
> -    Q_EVENT_SPICE_INITIALIZED,
> -    Q_EVENT_SPICE_DISCONNECTED,
> -    Q_EVENT_BLOCK_JOB_COMPLETED,
> -    Q_EVENT_BLOCK_JOB_CANCELLED,
> -    Q_EVENT_BLOCK_JOB_ERROR,
> -    Q_EVENT_BLOCK_JOB_READY,
> -    Q_EVENT_DEVICE_DELETED,
> -    Q_EVENT_DEVICE_TRAY_MOVED,
> -    Q_EVENT_NIC_RX_FILTER_CHANGED,
> -    Q_EVENT_SUSPEND,
> -    Q_EVENT_SUSPEND_DISK,
> -    Q_EVENT_WAKEUP,
> -    Q_EVENT_BALLOON_CHANGE,
> -    Q_EVENT_SPICE_MIGRATE_COMPLETED,
> -    Q_EVENT_GUEST_PANICKED,
> -    Q_EVENT_BLOCK_IMAGE_CORRUPTED,
> -
> -    /* Add to 'monitor_event_names' array in monitor.c when
> -     * defining new events here */
> -
> -    Q_EVENT_MAX,
> -} QEvent;
> -
>  int monitor_cur_is_qmp(void);
>  
>  void monitor_protocol_event(QEvent event, QObject *data);
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 60f3fd1..fbc1fab 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -29,6 +29,43 @@
>              'DeviceNotActive', 'DeviceNotFound', 'KVMMissingCap' ] }
>  
>  ##
> +# @QEvent

Again, see my comment in 3/6 wondering wheter we should fix the code
generation python to special-case QEVENT when converting this enum into
C code, rather than adding lots of churn.

I see why you split the documentation patch into 6/6 - to let this one
focus on just minimal code motion.
-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-10-21 20:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21  2:15 [Qemu-devel] [PATCH 0/6] qapi: generate event defines automatically Wenchao Xia
2013-10-21  2:16 ` [Qemu-devel] [PATCH 1/6] block: use type MonitorEvent directly Wenchao Xia
2013-10-21  2:16 ` [Qemu-devel] [PATCH 2/6] qapi: rename MonitorEvent to QEvent Wenchao Xia
2013-10-21 20:38   ` Eric Blake
2013-11-01 14:02   ` Luiz Capitulino
2013-11-01 14:21     ` [Qemu-devel] [libvirt] QEMU 1.6 and drive discard parameter Gareth Bult
2013-11-04  1:59     ` [Qemu-devel] [PATCH 2/6] qapi: rename MonitorEvent to QEvent Wenchao Xia
2013-11-04 13:33       ` Luiz Capitulino
2013-11-05  2:17         ` Wenchao Xia
2013-11-05  2:51           ` Luiz Capitulino
2013-11-05  5:31             ` Wenchao Xia
2013-11-05 14:06               ` Luiz Capitulino
2013-11-06  3:25                 ` Wenchao Xia
2013-10-21  2:16 ` [Qemu-devel] [PATCH 3/6] qapi: rename prefix QEVENT to Q_EVENT Wenchao Xia
2013-10-21 20:41   ` Eric Blake
2013-10-22  2:43     ` Wenchao Xia
2013-10-28 10:44     ` Paolo Bonzini
2013-10-29  5:22       ` Wenchao Xia
2013-10-29 16:09         ` Eric Blake
2013-10-30  7:26           ` Wenchao Xia
2013-11-01 14:06           ` Luiz Capitulino
2013-10-29 18:18     ` Kevin Wolf
2013-10-30  7:27       ` Wenchao Xia
2013-10-30 11:55         ` Paolo Bonzini
2013-10-31  5:26           ` Wenchao Xia
2013-10-21  2:16 ` [Qemu-devel] [PATCH 4/6] qapi: move event defines to qapi-schema.json Wenchao Xia
2013-10-21 20:45   ` Eric Blake [this message]
2013-10-21  2:16 ` [Qemu-devel] [PATCH 5/6] qapi: remove var monitor_event_names[] Wenchao Xia
2013-10-21 20:47   ` Eric Blake
2013-10-21  2:16 ` [Qemu-devel] [PATCH 6/6] qapi: add doc for QEvent Wenchao Xia
2013-10-21 21:00   ` Eric Blake
2013-10-22  3:19     ` Wenchao Xia
2013-10-22  3:46       ` Eric Blake
2013-10-23  0:37         ` Wenchao Xia
2013-10-29 23:02           ` Eric Blake
2013-10-30  7:51             ` Wenchao Xia
2013-10-22  6:55     ` Wenchao Xia
2013-10-22  7:33       ` Wenchao Xia
2013-10-22  8:58       ` Eric Blake
2013-10-25  9:16 ` [Qemu-devel] [PATCH 0/6] qapi: generate event defines automatically Wenchao Xia
2013-11-01 14:28 ` Luiz Capitulino
2013-11-04  1:54   ` Wenchao Xia

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=52659282.3050004@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xiawenc@linux.vnet.ibm.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 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.