From: Amit Shah <amit.shah@redhat.com>
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Amit Shah <amit.shah@redhat.com>
Subject: [PATCH v9 0/1] virtio-console: Support for generic ports and multiple consoles
Date: Tue, 20 Oct 2009 11:24:54 +0530 [thread overview]
Message-ID: <1256018095-19400-1-git-send-email-amit.shah@redhat.com> (raw)
Hello all,
Here is a new iteration of the patch series that implements a
transport for guest and host communications.
I've tested for compatibility (old qemu & new kernel, new qemu & old
kernel, new qemu & new kernel) and it all works fine. To maintain
backward compatibility, the first port to be spawned (port at id 0) is
to be a console port, to be bound to hvc. This keeps new host, old
guest happy.
A testsuite is put up at the following site that has an interactive
test program that can be run in the guest. It also has an automated
test suite that tests the major functionalities presented here:
http://fedorapeople.org/gitweb?p=amitshah/public_git/test-virtserial.git
This version passes all the automated tests there.
Christian has tested the console functionality on s390.
v9:
- Add debugfs files for each port to expose some port-specific information for
easier debugging
- Port hotplug fix
- Disallow opening of console ports (open(/dev/vcon0) should fail)
- A couple of other minor fixes.
Please review and apply,
Amit
Amit Shah (1):
virtio_console: Add support for multiple ports for generic guest and
host communication
drivers/char/Kconfig | 6 +
drivers/char/virtio_console.c | 1372 ++++++++++++++++++++++++++++++++++++----
include/linux/virtio_console.h | 50 ++-
3 files changed, 1292 insertions(+), 136 deletions(-)
next reply other threads:[~2009-10-20 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 5:54 Amit Shah [this message]
2009-10-20 5:54 ` [PATCH v9 1/1] virtio_console: Add support for multiple ports for generic guest and host communication 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=1256018095-19400-1-git-send-email-amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®