From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>, qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH 2/3] virtio-console: Add a virtio-serial bus, support for multiple devices and ports
Date: Mon, 04 Jan 2010 17:07:52 +0100 [thread overview]
Message-ID: <4B421258.8030803@redhat.com> (raw)
In-Reply-To: <m38wcsdbhf.fsf@crossbow.pond.sub.org>
On 12/24/09 09:26, Markus Armbruster wrote:
> We could declare that -virtioconsole always creates a bus a feature, but
> I can do that in good conscience only if the console created along with
> it always gets attached to it, even when other suitable buses exist.
I'd just discourage mixing -virtioconsole and -device virtio-serial-$bus
The whole point of -virtioconsole is backward compatibility for
management apps / start scripts and the like and it should create a
device which can be used by the guest like the qemu 0.11 virtioconsole.
If you are using device virtio-serial-$bus you are obviously not needing
the backward compatibility stuff ;)
cheers,
Gerd
prev parent reply other threads:[~2010-01-04 16:08 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 ` [Qemu-devel] " Anthony Liguori
[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 ` 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 [this message]
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=4B421258.8030803@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=armbru@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).