From: Jan Kiszka <jan.kiszka@siemens.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] virtio-serial: PCI device for simple host <-> guest communication
Date: Tue, 09 Jun 2009 19:15:25 +0200 [thread overview]
Message-ID: <4A2E98AD.2090904@siemens.com> (raw)
In-Reply-To: <1244565768-9103-4-git-send-email-amit.shah@redhat.com>
Amit Shah wrote:
> This interface presents a char device from which bits can be
> sent and read.
>
> Sample uses for such a device can be obtaining info from the
> guest like the file systems used, apps installed, etc. for
> offline usage and logged-in users, clipboard copy-paste, etc.
> for online usage.
Out of curiosity: What is the advantage over instantiating a multiport
16550A PCI card? Will those channels be so performance critical?
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-06-09 17:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 16:42 [Qemu-devel] [RFC] virtio-serial device Amit Shah
2009-06-09 16:42 ` [Qemu-devel] [PATCH] pci: add define for communication class devices Amit Shah
2009-06-09 16:42 ` [Qemu-devel] [PATCH] qdev: add virtserial char drv init hacks Amit Shah
2009-06-09 16:42 ` [Qemu-devel] [PATCH] virtio-serial: PCI device for simple host <-> guest communication Amit Shah
2009-06-09 17:15 ` Jan Kiszka [this message]
2009-06-09 18:15 ` [Qemu-devel] " Richard W.M. Jones
2009-06-09 19:19 ` Jan Kiszka
2009-06-09 18:17 ` [Qemu-devel] " Richard W.M. Jones
2009-06-09 18:47 ` Stuart Brady
2009-06-09 18:56 ` Anthony Liguori
2009-06-09 23:40 ` Paul Brook
2009-06-10 10:31 ` Amit Shah
2009-06-10 18:00 ` Jamie Lokier
2009-06-11 4:31 ` Amit Shah
2009-06-12 1:56 ` Jamie Lokier
2009-06-11 13:51 ` Amit Shah
2009-06-11 16:07 ` Blue Swirl
2009-06-11 16:21 ` Amit Shah
2009-06-10 10:28 ` 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=4A2E98AD.2090904@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amit.shah@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 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.