All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] virtio-serial: A guest <-> host interface for simple communication
Date: Tue, 23 Jun 2009 14:09:40 +0100	[thread overview]
Message-ID: <200906231409.41428.paul@codesourcery.com> (raw)
In-Reply-To: <20090623130023.GA32110@amit-x200.redhat.com>

On Tuesday 23 June 2009, Amit Shah wrote:
> On (Tue) Jun 23 2009 [13:55:52], Paul Brook wrote:
> > > Here are two patches. One implements a virtio-serial device in qemu
> > > and the other is the driver for a guest kernel.
> >
> > So I'll ask again. Why is this separate from virtio-console?
>
> I'm basically writing a vmchannel and found out that a lot can be shared
> between some virtio devices. So I'm just trying to abstract out those
> things in virtio-serial. Once we're sure virtio-serial is good and ready
> to be merged, I will look at converting over virtio-console to the
> virtio-serial interface.

That doesn't really answer my question. We already have a virtual serial 
device (called virtio-console). Why are you inventing another one?

Paul


WARNING: multiple messages have this Message-ID (diff)
From: Paul Brook <paul@codesourcery.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] virtio-serial: A guest <-> host interface for simple communication
Date: Tue, 23 Jun 2009 14:09:40 +0100	[thread overview]
Message-ID: <200906231409.41428.paul@codesourcery.com> (raw)
In-Reply-To: <20090623130023.GA32110@amit-x200.redhat.com>

On Tuesday 23 June 2009, Amit Shah wrote:
> On (Tue) Jun 23 2009 [13:55:52], Paul Brook wrote:
> > > Here are two patches. One implements a virtio-serial device in qemu
> > > and the other is the driver for a guest kernel.
> >
> > So I'll ask again. Why is this separate from virtio-console?
>
> I'm basically writing a vmchannel and found out that a lot can be shared
> between some virtio devices. So I'm just trying to abstract out those
> things in virtio-serial. Once we're sure virtio-serial is good and ready
> to be merged, I will look at converting over virtio-console to the
> virtio-serial interface.

That doesn't really answer my question. We already have a virtual serial 
device (called virtio-console). Why are you inventing another one?

Paul

  reply	other threads:[~2009-06-23 13:09 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 12:42 virtio-serial: A guest <-> host interface for simple communication Amit Shah
2009-06-23 12:42 ` [Qemu-devel] " Amit Shah
2009-06-23 12:42 ` [PATCH] virtio_serial: A char device for simple guest <-> host communication Amit Shah
2009-06-23 12:42   ` [Qemu-devel] " Amit Shah
2009-06-23 12:42   ` [PATCH] virtio-serial: virtio device for simple host <-> guest communication Amit Shah
2009-06-23 12:42   ` Amit Shah
2009-06-23 12:42     ` [Qemu-devel] " Amit Shah
2009-06-23 15:19     ` Blue Swirl
2009-06-23 15:19       ` Blue Swirl
2009-06-23 15:19     ` Blue Swirl
2009-06-23 15:15   ` [Qemu-devel] [PATCH] virtio_serial: A char device for simple guest <-> host communication Blue Swirl
2009-06-23 15:15   ` Blue Swirl
2009-06-23 15:15     ` Blue Swirl
2009-06-23 12:42 ` Amit Shah
2009-06-23 12:55 ` [Qemu-devel] virtio-serial: A guest <-> host interface for simple communication Paul Brook
2009-06-23 12:55 ` Paul Brook
2009-06-23 12:55   ` Paul Brook
2009-06-23 13:00   ` Amit Shah
2009-06-23 13:00   ` Amit Shah
2009-06-23 13:00     ` Amit Shah
2009-06-23 13:09     ` Paul Brook [this message]
2009-06-23 13:09       ` Paul Brook
2009-06-23 13:09     ` Paul Brook
2009-06-23 13:58   ` Christian Bornträger
2009-06-23 13:58   ` Christian Bornträger
2009-06-23 13:58     ` Christian Bornträger
2009-06-23 14:16     ` Paul Brook
2009-06-23 14:16     ` Paul Brook
2009-06-23 14:16       ` Paul Brook
2009-06-23 14:40       ` Christian Bornträger
2009-06-23 14:40       ` Christian Bornträger
2009-06-23 14:40         ` Christian Bornträger
2009-06-23 14:59   ` Daniel P. Berrange
2009-06-24  4:15 ` Rusty Russell
2009-06-24  4:15   ` [Qemu-devel] " Rusty Russell
2009-06-24 12:39   ` Amit Shah
2009-06-24 12:39   ` Amit Shah
2009-06-24 12:39     ` [Qemu-devel] " Amit Shah
2009-06-25 11:33     ` Rusty Russell
2009-06-25 11:33     ` Rusty Russell
2009-06-25 11:33       ` [Qemu-devel] " Rusty Russell
2009-06-25 20:49       ` Amit Shah
2009-06-25 20:49         ` [Qemu-devel] " Amit Shah
2009-06-24  4:15 ` Rusty Russell
2009-06-24 16:40 ` [Qemu-devel] " Jamie Lokier
2009-06-24 17:10   ` Amit Shah
2009-06-24 17:10     ` Amit Shah
2009-06-24 17:50     ` Jamie Lokier
2009-06-24 17:50       ` Jamie Lokier
2009-06-24 18:01       ` Amit Shah
2009-06-24 18:01       ` Amit Shah
2009-06-24 18:01         ` Amit Shah
2009-06-24 19:20         ` Jamie Lokier
2009-06-24 19:20         ` Jamie Lokier
2009-06-24 19:20           ` Jamie Lokier
2009-06-25  4:41           ` Amit Shah
2009-06-25  4:41           ` Amit Shah
2009-06-25  4:41             ` Amit Shah
2009-06-24 17:50     ` Jamie Lokier
2009-06-24 17:10   ` 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=200906231409.41428.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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 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.