All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Lepton Wu <ytht.net@gmail.com>,
	virtualization@lists.linux-foundation.org
Cc: mst@redhat.com
Subject: Re: [PATCH 0/1] Add uvirtio for testing
Date: Wed, 29 Apr 2020 17:56:47 +0800	[thread overview]
Message-ID: <b01454e9-bca8-cf32-7cfa-ebe25032e040@redhat.com> (raw)
In-Reply-To: <20200428204729.64569-1-ytht.net@gmail.com>


On 2020/4/29 上午4:47, Lepton Wu wrote:
> This is a way to create virtio based devices from user space. This is the
> background for this patch:
>
> We have some images works fine under qemu, we'd like to also run the same image
> on Google Cloud. Currently Google Cloud doesn't support virtio-vga. I had a
> patch to create a virtio-vga from kernel directly:
> https://www.spinics.net/lists/dri-devel/msg248573.html
>
> Then I got feedback from Gerd that maybe it's better to change that to something
> like uvirtio. Since I really don't have other use cases for now, I just implemented the minimal stuff which work for my use case.


Interesting, several questions:

1) Are you aware of virtio vhost-user driver done by UM guys? 
(arch/um/drivers/virtio_uml.c) The memory part is tricky but overall 
both of you have similar target.
2) Patch 1 said it's userspace virtio driver, which I think it is 
actually "userspace virtio device"
3) Need to be verbose on how the vring processing work in the commit log 
of patch 1
4) I'm curious which testing you want to accomplish through this new 
transport, I guess you want to test a specific virtio driver?
5) You mentioned that you may want to develop communication between 
kernel and userspace, any more details on that?

Thanks


>
> Lepton Wu (1):
>    virtio: Add uvirtio driver
>
>   drivers/virtio/Kconfig        |   8 +
>   drivers/virtio/Makefile       |   1 +
>   drivers/virtio/uvirtio.c      | 405 ++++++++++++++++++++++++++++++++++
>   include/linux/uvirtio.h       |   8 +
>   include/uapi/linux/uvirtio.h  |  69 ++++++
>   samples/uvirtio/Makefile      |   9 +
>   samples/uvirtio/uvirtio-vga.c |  63 ++++++
>   7 files changed, 563 insertions(+)
>   create mode 100644 drivers/virtio/uvirtio.c
>   create mode 100644 include/linux/uvirtio.h
>   create mode 100644 include/uapi/linux/uvirtio.h
>   create mode 100644 samples/uvirtio/Makefile
>   create mode 100644 samples/uvirtio/uvirtio-vga.c
>

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2020-04-29  9:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 20:47 [PATCH 0/1] Add uvirtio for testing Lepton Wu
2020-04-28 20:47 ` [PATCH 1/1] virtio: Add uvirtio driver Lepton Wu
2020-04-29  9:56 ` Jason Wang [this message]
2020-04-29 11:58   ` [PATCH 0/1] Add uvirtio for testing Gerd Hoffmann
2020-04-30  3:59     ` lepton
2020-04-30  7:51       ` Gerd Hoffmann
2020-05-01  0:57         ` [PATCH v3] virtio: Add uvirtio driver Lepton Wu
2020-05-01  0:59         ` [PATCH 0/1] Add uvirtio for testing lepton
2020-04-30  3:55   ` [PATCH v2] virtio: Add uvirtio driver Lepton Wu
2020-04-30  3:56   ` [PATCH 0/1] Add uvirtio for testing lepton
2020-05-06  3:14     ` Jason Wang

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=b01454e9-bca8-cf32-7cfa-ebe25032e040@redhat.com \
    --to=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=ytht.net@gmail.com \
    /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.