From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: Extending virtio_console to support multiple ports
Date: Mon, 31 Aug 2009 11:37:05 -0500 [thread overview]
Message-ID: <4A9BFC31.9070005@codemonkey.ws> (raw)
In-Reply-To: <20090831161925.GA22928@amit-x200.redhat.com>
Amit Shah wrote:
>>> We're ending up having to compromise on the performance or functionality
>>> or simplicity the devices just because of this restriction.
>>>
>>>
>> This is _not_ a high performance device and there so far has been no
>> functionality impact. I don't understand why you keep dragging your
>> feet about this. It's very simple, if you post a functional set of
>> patches for a converged virtio-console driver, we'll merge it. If you
>>
>
> I have already posted them and have received no feedback about the
> patches since. Let me add another request here for you to review them.
>
But the guest drivers do not have proper locking. Have you posted a new
series with that fixed?
>> keep arguing about having a separate virtio-serial driver, it's not
>> going to get merged. I don't know how to be more clear than this.
>>
>
> I'm not at all arguing for a separate virtio-serial driver. Please note
> the difference in what I'm asking for: I'm just asking for a good
> justification for the merging of the two since it just makes both the
> drivers not simple and also introduces dependencies on code outside our
> control.
>
Functionally speaking, both virtio-console and virtio-serial do the same
thing. In fact, virtio-console is just a subset of virtio-serial.
If there are problems converging the two drivers in Linux, then I
suggest you have two separate driver modules in Linux. That would
obviously be rejected for Linux though because you cannot have two
drivers for the same device. Why should qemu have a different policy?
>> That is not a justification to add a new device in QEMU. If we add a
>> new device everytime we encounter a less than ideal interface within a
>> guest, we're going to end up having hundreds of devices.
>>
>
> I just find this argument funny.
>
I'm finding this discussion not so productive.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-08-31 16:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 6:17 [Qemu-devel] Extending virtio_console to support multiple ports Amit Shah
2009-08-25 6:17 ` [Qemu-devel] [PATCH] virtio_console: Add interface for guest and host communication Amit Shah
2009-08-25 6:17 ` [Qemu-devel] [PATCH 1/3] char: Emit 'CLOSED' events on char device close Amit Shah
2009-08-25 6:17 ` [Qemu-devel] [PATCH 2/3] virtio-console: rename dvq to ovq Amit Shah
2009-08-25 8:16 ` [Qemu-devel] [PATCH 3/3] virtio-console: Add interface for generic guest-host communication Amit Shah
2009-08-26 11:27 ` [Qemu-devel] Re: Extending virtio_console to support multiple ports Amit Shah
2009-08-26 15:45 ` Amit Shah
2009-08-27 4:07 ` Benjamin Herrenschmidt
2009-08-27 6:51 ` Amit Shah
2009-08-27 9:08 ` Alan Cox
2009-08-27 9:27 ` Benjamin Herrenschmidt
2009-08-27 11:45 ` [Qemu-devel] [PATCH] hvc_console: provide (un)locked version for hvc_resize() Hendrik Brueckner
2009-08-29 1:15 ` [Qemu-devel] Re: Extending virtio_console to support multiple ports Jamie Lokier
2009-08-27 5:04 ` Michael Ellerman
2009-08-27 6:52 ` Amit Shah
2009-08-27 14:13 ` Ryan Arnold
2009-08-28 17:00 ` Anthony Liguori
2009-08-30 10:10 ` Amit Shah
2009-08-30 12:48 ` Anthony Liguori
2009-08-30 13:17 ` Amit Shah
2009-08-31 13:17 ` Anthony Liguori
2009-08-31 13:51 ` Amit Shah
2009-08-31 14:21 ` Anthony Liguori
2009-08-31 14:31 ` Amit Shah
2009-08-31 15:56 ` Anthony Liguori
2009-08-31 16:19 ` Amit Shah
2009-08-31 16:37 ` Anthony Liguori [this message]
2009-09-21 5:20 ` Rusty Russell
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=4A9BFC31.9070005@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).