From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: agraf@suse.de, kraxel@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] virtio-console: Add a virtio-serial bus, support for multiple devices and ports
Date: Tue, 22 Dec 2009 15:19:00 -0600 [thread overview]
Message-ID: <4B3137C4.5090403@codemonkey.ws> (raw)
In-Reply-To: <1261504146-26018-3-git-send-email-amit.shah@redhat.com>
On 12/22/2009 11:49 AM, Amit Shah wrote:
> This patch migrates virtio-console to the qdev infrastructure and
> creates a new virtio-serial bus on which multiple ports are exposed as
> devices. The bulk of the code now resides in a new file with
> virtio-console.c being just a simple qdev device.
>
> This interface enables spawning of multiple virtio consoles as well as generic
> serial ports.
>
> The older -virtconsole argument still works, but when using the new
> functionality, it is recommended to use
>
> -device virtio-serial-pci -device virtconsole,...
>
> The virtconsole device type accepts a chardev as an argument and a 'name'
> argument to identify the corresponding consoles on the host as well as the
> guest. The name, if given, is exposed via the 'name' sysfs attribute in the
> guest.
>
> Care has been taken to ensure compatibility with kernels that do not
> support multiple ports as well as accepting incoming migrations from older
> qemu versions.
>
> Signed-off-by: Amit Shah<amit.shah@redhat.com>
This is really difficult to review. If you're introducing a completely
new file, why don't you just call it virtio-serial.c and delete
virtio-console.c It will save quite a bit of reviewing head ache.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-22 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 17:49 [Qemu-devel] [RFC PATCH 0/3] virtio-console: Move to qdev, multiple devices, generic ports Amit Shah
2009-12-22 17:49 ` [Qemu-devel] [PATCH 1/3] virtio: Remove duplicate macro definition for max. virtqueues, bump up the max Amit Shah
2009-12-22 17:49 ` [Qemu-devel] [PATCH 2/3] virtio-console: Add a virtio-serial bus, support for multiple devices and ports Amit Shah
2009-12-22 17:49 ` [Qemu-devel] [PATCH 3/3] virtio-serial: Add a new virtserialport device for generic serial port support Amit Shah
2009-12-22 17:55 ` [Qemu-devel] Re: [PATCH 2/3] virtio-console: Add a virtio-serial bus, support for multiple devices and ports Alexander Graf
2009-12-22 17:59 ` Amit Shah
2009-12-22 18:08 ` Alexander Graf
2009-12-22 18:16 ` Amit Shah
2009-12-22 21:19 ` Anthony Liguori [this message]
[not found] ` <m33a31lrrk.fsf@crossbow.pond.sub.org>
[not found] ` <20091223150732.GA15932@amit-x200.redhat.com>
[not found] ` <m3aax9ikec.fsf@crossbow.pond.sub.org>
2010-01-04 9:23 ` [Qemu-devel] " Gerd Hoffmann
[not found] ` <20091223194020.GA22864@amit-x200.redhat.com>
[not found] ` <m3fx71fioz.fsf@crossbow.pond.sub.org>
[not found] ` <20091224051415.GA25261@amit-x200.redhat.com>
[not found] ` <m38wcsdbhf.fsf@crossbow.pond.sub.org>
2010-01-04 16:07 ` Gerd Hoffmann
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=4B3137C4.5090403@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@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).