qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Amit Shah <amit.shah@redhat.com>, qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 2/7] virtio-serial: Disallow generic ports at id 0
Date: Mon, 21 Mar 2011 18:39:17 +0530	[thread overview]
Message-ID: <0b8b716d6c43b5a1d4e0293df1c77af4fff21bab.1300712809.git.amit.shah@redhat.com> (raw)
In-Reply-To: <cover.1300712809.git.amit.shah@redhat.com>
In-Reply-To: <cover.1300712809.git.amit.shah@redhat.com>

Port 0 is reserved for virtconsole devices for backward compatibility
with the old -virtioconsole (from qemu 0.12) device type.

libvirt prior to commit 8e28c5d40200b4c5d483bd585d237b9d870372e5 used
port 0 for generic ports.  libvirt will no longer do that, but disallow
instantiating generic ports at id 0 from qemu as well.

Signed-off-by: Amit Shah <amit.shah@redhat.com>
---
 hw/virtio-console.c |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/hw/virtio-console.c b/hw/virtio-console.c
index c235b27..4440784 100644
--- a/hw/virtio-console.c
+++ b/hw/virtio-console.c
@@ -11,6 +11,7 @@
  */
 
 #include "qemu-char.h"
+#include "qemu-error.h"
 #include "virtio-serial.h"
 
 typedef struct VirtConsole {
@@ -113,6 +114,14 @@ static int virtserialport_initfn(VirtIOSerialPort *port)
 {
     VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port);
 
+    if (port->id == 0) {
+        /*
+         * Disallow a generic port at id 0, that's reserved for
+         * console ports.
+         */
+        error_report("Port number 0 on virtio-serial devices reserved for virtconsole devices for backward compatibility.");
+        return -1;
+    }
     return generic_port_init(vcon, port);
 }
 
-- 
1.7.4

  parent reply	other threads:[~2011-03-21 13:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 13:09 [Qemu-devel] [PULL #7 0/7] virtio-serial fixes, enhancements Amit Shah
2011-03-21 13:09 ` [Qemu-devel] [PATCH 1/7] virtio-serial: Use a struct to pass config information from proxy Amit Shah
2011-03-23 13:26   ` [Qemu-devel] " Juan Quintela
2011-03-21 13:09 ` Amit Shah [this message]
2011-03-21 13:09 ` [Qemu-devel] [PATCH 3/7] virtio-serial: Enable ioeventfd Amit Shah
2011-03-21 13:09 ` [Qemu-devel] [PATCH 4/7] virtio-serial-bus: Simplify handle_output() function Amit Shah
2011-03-21 13:09 ` [Qemu-devel] [PATCH 5/7] virtio-serial: Don't clear ->have_data() pointer after unplug Amit Shah
2011-03-23 13:33   ` [Qemu-devel] " Juan Quintela
2011-03-23 13:39     ` Amit Shah
2011-03-21 13:09 ` [Qemu-devel] [PATCH 6/7] virtio-console: Keep chardev open for other users after hot-unplug Amit Shah
2011-03-21 13:09 ` [Qemu-devel] [PATCH 7/7] char: Prevent multiple devices opening same chardev Amit Shah
2011-03-23 13:32   ` [Qemu-devel] " Juan Quintela
2011-03-23 13:31 ` [Qemu-devel] Re: [PULL #7 0/7] virtio-serial fixes, enhancements Juan Quintela
2011-03-23 13:40   ` 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=0b8b716d6c43b5a1d4e0293df1c77af4fff21bab.1300712809.git.amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).