virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: Arnaud POULIQUEN <arnaud.pouliquen@st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Vincent Whitchurch <vincent.whitchurch@axis.com>,
	"linux-remoteproc@vger.kernel.org"
	<linux-remoteproc@vger.kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	"sound-open-firmware@alsa-project.org"
	<sound-open-firmware@alsa-project.org>
Subject: Re: [PATCH v6 0/4] Add a vhost RPMsg API
Date: Thu, 17 Sep 2020 07:47:06 +0200	[thread overview]
Message-ID: <20200917054705.GA11491@ubuntu> (raw)
In-Reply-To: <9433695b-5757-db73-bd8a-538fd1375e2a@st.com>

Hi Arnaud,

On Tue, Sep 15, 2020 at 02:13:23PM +0200, Arnaud POULIQUEN wrote:
> Hi  Guennadi,
> 
> On 9/1/20 5:11 PM, Guennadi Liakhovetski wrote:
> > Hi,
> > 
> > Next update:
> > 
> > v6:
> > - rename include/linux/virtio_rpmsg.h -> include/linux/rpmsg/virtio.h
> > 
> > v5:
> > - don't hard-code message layout
> > 
> > v4:
> > - add endianness conversions to comply with the VirtIO standard
> > 
> > v3:
> > - address several checkpatch warnings
> > - address comments from Mathieu Poirier
> > 
> > v2:
> > - update patch #5 with a correct vhost_dev_init() prototype
> > - drop patch #6 - it depends on a different patch, that is currently
> >   an RFC
> > - address comments from Pierre-Louis Bossart:
> >   * remove "default n" from Kconfig
> > 
> > Linux supports RPMsg over VirtIO for "remote processor" / AMP use
> > cases. It can however also be used for virtualisation scenarios,
> > e.g. when using KVM to run Linux on both the host and the guests.
> > This patch set adds a wrapper API to facilitate writing vhost
> > drivers for such RPMsg-based solutions. The first use case is an
> > audio DSP virtualisation project, currently under development, ready
> > for review and submission, available at
> > https://github.com/thesofproject/linux/pull/1501/commits
> 
> Mathieu pointed me your series. On my side i proposed the rpmsg_ns_msg
> service[1] that does not match with your implementation.
> As i come late, i hope that i did not miss something in the history...
> Don't hesitate to point me the discussions, if it is the case.

Well, as you see, this is a v6 only of this patch set, and apart from it 
there have been several side discussions and patch sets.

> Regarding your patchset, it is quite confusing for me. It seems that you
> implement your own protocol on top of vhost forked from the RPMsg one.
> But look to me that it is not the RPMsg protocol.

I'm implementing a counterpart to the rpmsg protocol over VirtIO as 
initially implemented by drivers/rpmsg/virtio_rpmsg_bus.c for the "main 
CPU" (in case of remoteproc over VirtIO) or the guest side in case of 
Linux virtualisation. Since my implementation can talk to that driver, 
I don't think, that I'm inventing a new protocol. I'm adding support 
for the same protocol for the opposite side of the VirtIO divide.

> So i would be agree with Vincent[2] which proposed to switch on a RPMsg API
> and creating a vhost rpmsg device. This is also proposed in the 
> "Enhance VHOST to enable SoC-to-SoC communication" RFC[3].
> Do you think that this alternative could match with your need?

As I replied to Vincent, I understand his proposal and the approach taken 
in the series [3], but I'm not sure I agree, that adding yet another 
virtual device / driver layer on the vhost side is a good idea. As far as 
I understand adding new completely virtual devices isn't considered to be 
a good practice in the kernel. Currently vhost is just a passive "library" 
and my vhost-rpmsg support keeps it that way. Not sure I'm in favour of 
converting vhost to a virtual device infrastructure.

Thanks for pointing me out at [3], I should have a better look at it.

Thanks
Guennadi

> [1]. https://patchwork.kernel.org/project/linux-remoteproc/list/?series=338335 
> [2]. https://www.spinics.net/lists/linux-virtualization/msg44195.html
> [3]. https://www.spinics.net/lists/linux-remoteproc/msg06634.html  
> 
> Thanks,
> Arnaud
> 
> > 
> > Thanks
> > Guennadi
> > 
> > Guennadi Liakhovetski (4):
> >   vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl
> >   rpmsg: move common structures and defines to headers
> >   rpmsg: update documentation
> >   vhost: add an RPMsg API
> > 
> >  Documentation/rpmsg.txt          |   6 +-
> >  drivers/rpmsg/virtio_rpmsg_bus.c |  78 +------
> >  drivers/vhost/Kconfig            |   7 +
> >  drivers/vhost/Makefile           |   3 +
> >  drivers/vhost/rpmsg.c            | 373 +++++++++++++++++++++++++++++++
> >  drivers/vhost/vhost_rpmsg.h      |  74 ++++++
> >  include/linux/rpmsg/virtio.h     |  83 +++++++
> >  include/uapi/linux/rpmsg.h       |   3 +
> >  include/uapi/linux/vhost.h       |   4 +-
> >  9 files changed, 551 insertions(+), 80 deletions(-)
> >  create mode 100644 drivers/vhost/rpmsg.c
> >  create mode 100644 drivers/vhost/vhost_rpmsg.h
> >  create mode 100644 include/linux/rpmsg/virtio.h
> > 
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2020-09-17  5:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 15:11 [PATCH v6 0/4] Add a vhost RPMsg API Guennadi Liakhovetski
2020-09-01 15:11 ` [PATCH v6 1/4] vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl Guennadi Liakhovetski
2020-09-01 15:11 ` [PATCH v6 2/4] rpmsg: move common structures and defines to headers Guennadi Liakhovetski
     [not found]   ` <20200901172321.GC236120@xps15>
2020-09-02  5:35     ` Guennadi Liakhovetski
     [not found]       ` <20200902172437.GC280378@xps15>
2020-09-03  5:51         ` Guennadi Liakhovetski
2020-09-01 15:11 ` [PATCH v6 3/4] rpmsg: update documentation Guennadi Liakhovetski
2020-09-01 15:11 ` [PATCH v6 4/4] vhost: add an RPMsg API Guennadi Liakhovetski
2020-09-15 12:13 ` [PATCH v6 0/4] Add a vhost " Arnaud POULIQUEN
2020-09-17  5:47   ` Guennadi Liakhovetski [this message]
2020-09-17  8:36     ` Vincent Whitchurch
2020-09-17 10:29       ` Guennadi Liakhovetski
2020-09-17 15:21     ` Arnaud POULIQUEN
2020-09-18  5:44       ` Guennadi Liakhovetski
2020-09-18  7:47         ` Arnaud POULIQUEN
2020-09-18  9:47           ` Guennadi Liakhovetski
2020-09-18 10:39             ` Vincent Whitchurch
2020-09-18 11:02               ` Guennadi Liakhovetski
2020-09-18 17:26             ` Arnaud POULIQUEN

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=20200917054705.GA11491@ubuntu \
    --to=guennadi.liakhovetski@linux.intel.com \
    --cc=arnaud.pouliquen@st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mst@redhat.com \
    --cc=ohad@wizery.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=vincent.whitchurch@axis.com \
    --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).