qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org, mprivozn@redhat.com, kraxel@redhat.com,
	amit.shah@redhat.com, eblake@redhat.com, lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH for-2.1 v2 1/2] virtio-serial: report frontend connection state via monitor
Date: Thu, 26 Jun 2014 13:11:14 +0200	[thread overview]
Message-ID: <1403781075-30989-2-git-send-email-lersek@redhat.com> (raw)
In-Reply-To: <1403781075-30989-1-git-send-email-lersek@redhat.com>

Libvirt wants to know about the guest-side connection state of some
virtio-serial ports (in particular the one(s) assigned to guest agent(s)).
Report such states with a new monitor event.

RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1080376
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---

Notes:
    v2:
    - emit event unconditionally; drop per-port "report_connstate" property
      [Eric]
    - rate-limit the new event [Eric] -- unify it with other
      guest-triggerable events in monitor_qapi_event_init()
    - rebased to Wenchao's qapi-event series
    - introduce one event only, VSERPORT_CHANGE, and make the port status a
      parameter [Eric]

 qapi-event.json          | 16 ++++++++++++++++
 qapi-schema.json         | 16 ++++++++++++++++
 hw/char/virtio-console.c | 15 ++++++++++++---
 monitor.c                |  1 +
 4 files changed, 45 insertions(+), 3 deletions(-)

diff --git a/qapi-event.json b/qapi-event.json
index e7a47f9..0ec20c4 100644
--- a/qapi-event.json
+++ b/qapi-event.json
@@ -315,4 +315,20 @@
 ##
 { 'event': 'QUORUM_REPORT_BAD',
   'data': { '*error': 'str', 'node-name': 'str',
             'sector-num': 'int', 'sector-count': 'int' } }
+
+##
+# @VSERPORT_CHANGE
+#
+# Emitted when the guest takes an action that changes the status of a
+# virtio-serial port (eg. opens or closes it).
+#
+# @id: device identifier of the virtio-serial port
+#
+# @status: new status of the virtio-serial port
+#
+# Since: 2.1
+##
+{ 'event': 'VSERPORT_CHANGE',
+  'data': { 'id': 'str',
+            'status': 'VirtioSerialPortStatus' } }
diff --git a/qapi-schema.json b/qapi-schema.json
index e7727a1..d1dc8be 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -3398,5 +3398,21 @@
 ##
 { 'enum': 'GuestPanicAction',
   'data': [ 'pause' ] }
 
+##
+# @VirtioSerialPortStatus
+#
+# An enumeration of the possible / recognized states of virtio-serial ports.
+#
+# @connected: the virtio-serial port has been opened (connected to) in the
+#              guest.
+#
+# @disconnected: the virtio-serial port has been closed (disconnected from) in
+#                the guest.
+#
+# Since: 2.1
+##
+{ 'enum': 'VirtioSerialPortStatus',
+  'data': [ 'connected', 'disconnected' ] }
+
 { 'include': 'qapi-event.json' }
diff --git a/hw/char/virtio-console.c b/hw/char/virtio-console.c
index 6c8be0f..729faac 100644
--- a/hw/char/virtio-console.c
+++ b/hw/char/virtio-console.c
@@ -13,8 +13,9 @@
 #include "sysemu/char.h"
 #include "qemu/error-report.h"
 #include "trace.h"
 #include "hw/virtio/virtio-serial.h"
+#include "qapi-event.h"
 
 #define TYPE_VIRTIO_CONSOLE_SERIAL_PORT "virtserialport"
 #define VIRTIO_CONSOLE(obj) \
     OBJECT_CHECK(VirtConsole, (obj), TYPE_VIRTIO_CONSOLE_SERIAL_PORT)
@@ -80,13 +81,21 @@ static ssize_t flush_buf(VirtIOSerialPort *port,
 /* Callback function that's called when the guest opens/closes the port */
 static void set_guest_connected(VirtIOSerialPort *port, int guest_connected)
 {
     VirtConsole *vcon = VIRTIO_CONSOLE(port);
+    DeviceState *dev = DEVICE(port);
 
-    if (!vcon->chr) {
-        return;
+    if (vcon->chr) {
+        qemu_chr_fe_set_open(vcon->chr, guest_connected);
+    }
+
+    if (dev->id) {
+        VirtioSerialPortStatus status = guest_connected ?
+            VIRTIO_SERIAL_PORT_STATUS_CONNECTED :
+            VIRTIO_SERIAL_PORT_STATUS_DISCONNECTED;
+
+        qapi_event_send_vserport_change(dev->id, status, &error_abort);
     }
-    qemu_chr_fe_set_open(vcon->chr, guest_connected);
 }
 
 /* Readiness of the guest to accept data on a port */
 static int chr_can_read(void *opaque)
diff --git a/monitor.c b/monitor.c
index a8ab600..5fbf987 100644
--- a/monitor.c
+++ b/monitor.c
@@ -584,8 +584,9 @@ static void monitor_qapi_event_init(void)
     /* Limit guest-triggerable events to 1 per second */
     monitor_qapi_event_throttle(QAPI_EVENT_RTC_CHANGE, 1000);
     monitor_qapi_event_throttle(QAPI_EVENT_WATCHDOG, 1000);
     monitor_qapi_event_throttle(QAPI_EVENT_BALLOON_CHANGE, 1000);
+    monitor_qapi_event_throttle(QAPI_EVENT_VSERPORT_CHANGE, 1000);
     /* limit the rate of quorum events to avoid hammering the management */
     monitor_qapi_event_throttle(QAPI_EVENT_QUORUM_REPORT_BAD, 1000);
     monitor_qapi_event_throttle(QAPI_EVENT_QUORUM_FAILURE, 1000);
 
-- 
1.8.3.1

  reply	other threads:[~2014-06-26 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 11:11 [Qemu-devel] [PATCH for-2.1 v2 0/2] help libvirt know what's up with qga Laszlo Ersek
2014-06-26 11:11 ` Laszlo Ersek [this message]
2014-06-26 12:15   ` [Qemu-devel] [PATCH for-2.1 v2 1/2] virtio-serial: report frontend connection state via monitor Eric Blake
2014-06-26 11:11 ` [Qemu-devel] [PATCH for-2.1 v2 2/2] char: report frontend open/closed state in 'query-chardev' Laszlo Ersek
2014-06-26 12:09   ` Eric Blake
2014-06-26 13:38     ` Laszlo Ersek
2014-06-26 15:09       ` Eric Blake
2014-06-26 11:30 ` [Qemu-devel] [PATCH for-2.1 v2 0/2] help libvirt know what's up with qga Amit Shah

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=1403781075-30989-2-git-send-email-lersek@redhat.com \
    --to=lersek@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mprivozn@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).