All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, Anthony Liguori <aliguori@us.ibm.com>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH][RFC] vmchannel a data channel between host and guest.
Date: Mon, 13 Oct 2008 13:32:35 -0500	[thread overview]
Message-ID: <48F39443.4070203@codemonkey.ws> (raw)
In-Reply-To: <20081012124534.GK11435@redhat.com>

Gleb Natapov wrote:
> Hello,
>
>  Sometimes there is a need to pass various bits of information between host
> and guest (mostly for management purposes such as host screen resolution
> changes or runtime statistics of a guest). To do that we need some way to
> pass data between host and guest. Attached patch implements vmchannel that can
> be used for this purpose. It is based on virtio infrastructure and
> support more then one channel. The vmchannel presents itself as PCI
> device to a guest so guest driver is also required. The one for linux is
> attached. It uses netlink connector to communicate with userspace.
>   

Essentially, the transport itself ends up looking very much like a 
network device so the only real design question is what the guest and 
host interfaces look like.  I don't know that a netlink interface is the 
best interface to userspace.  Why not a full blown socket?  Perhaps a 
virtual file system?

Having a limit of only 4 links seems like a problem to me too.

I think there needs to be a better articulation about why other 
interfaces cannot be used (like a network device).  Is it because of 
ease of guest configuration?  Is it performance?

Regards,

Anthony Liguori

> Comments are welcome.
>
> --
> 			Gleb.
>   


  reply	other threads:[~2008-10-13 18:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12 12:45 [PATCH][RFC] vmchannel a data channel between host and guest Gleb Natapov
2008-10-13 18:32 ` Anthony Liguori [this message]
2008-10-14  9:05   ` Gleb Natapov
2008-10-14 13:50     ` Anthony Liguori
2008-10-14 17:59       ` Gleb Natapov
2008-10-14 18:16         ` Anthony Liguori
2008-10-15 12:58           ` Gleb Natapov
2008-10-15 14:02             ` Anthony Liguori
2008-10-16  8:41               ` Gleb Natapov
2008-10-15 14:02             ` Anthony Liguori
2008-10-15 14:18             ` Andrew Biggadike
2008-10-15 14:18             ` Andrew Biggadike
2008-10-15 14:30               ` Gleb Natapov
2008-10-15 14:30               ` Gleb Natapov
2008-10-15 15:00                 ` Andrew Biggadike
2008-10-15 15:42               ` Gleb Natapov
2008-10-15 15:56                 ` Anthony Liguori
2008-10-16  8:54                   ` Gleb Natapov
2008-10-15 15:56                 ` Anthony Liguori
2008-10-15 16:59                 ` Andrew Biggadike
2008-10-15 16:59                 ` Andrew Biggadike
2008-10-15 12:58           ` Gleb Natapov
2008-10-14 18:16         ` Anthony Liguori

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=48F39443.4070203@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.