From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: Arnaud POULIQUEN <arnaud.pouliquen@st.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"sound-open-firmware@alsa-project.org"
<sound-open-firmware@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH v6 0/4] Add a vhost RPMsg API
Date: Fri, 18 Sep 2020 13:02:49 +0200 [thread overview]
Message-ID: <20200918110249.GE19246@ubuntu> (raw)
In-Reply-To: <20200918103907.2ts4l5xiwm4542rs@axis.com>
On Fri, Sep 18, 2020 at 12:39:07PM +0200, Vincent Whitchurch wrote:
> On Fri, Sep 18, 2020 at 11:47:20AM +0200, Guennadi Liakhovetski wrote:
> > On Fri, Sep 18, 2020 at 09:47:45AM +0200, Arnaud POULIQUEN wrote:
> > > IMO, as this API is defined in the Linux documentation [5] we should respect it, to ensure
> > > one generic implementation. The RPMsg sample client[4] uses this user API, so seems to me
> > > a good candidate to verify this.
> > >
> > > That's said, shall we multiple the RPMsg implementations in Linux with several APIs,
> > > With the risk to make the RPMsg clients devices dependent on these implementations?
> > > That could lead to complex code or duplications...
> >
> > So, no, in my understanding there aren't two competing alternative APIs, you'd never have
> > to choose between them. If you're writing a driver for Linux to communicate with remote
> > processors or to run on VMs, you use the existing API. If you're writing a driver for
> > Linux to communicate with those VMs, you use the vhost API and whatever help is available
> > for RPMsg processing.
> >
> > However, I can in principle imagine a single driver, written to work on both sides.
> > Something like the rpmsg_char.c or maybe some networking driver. Is that what you're
> > referring to? I can see that as a fun exercise, but are there any real uses for that?
>
> I hinted at a real use case for this in the previous mail thread[0].
> I'm exploring using rpmsg-char to allow communication between two chips,
> both running Linux. rpmsg-char can be used pretty much as-is for both
> sides of the userspace-to-userspace communication and (the userspace
> side of the) userspace-to-kernel communication between the two chips.
>
> > You could do the same with VirtIO, however, it has been decided to go with two
> > distinct APIs: virtio for guests and vhost for the host, noone bothered to create a
> > single API for both and nobody seems to miss one. Why would we want one with RPMsg?
>
> I think I answered this question in the previous mail thread as well[1]:
> | virtio has distinct driver and device roles so the completely different
> | APIs on each side are understandable. But I don't see that distinction
> | in the rpmsg API which is why it seems like a good idea to me to make it
> | work from both sides of the link and allow the reuse of drivers like
> | rpmsg-char, instead of imposing virtio's distinction on rpmsg.
I think RPMsg is lacking real established documentation... Quating from [2]:
<quote>
In the current protocol, at startup, the master sends notification to remote to let it
know that it can receive name service announcement.
</quote>
Isn't that a sufficient asymnetry?
Thanks
Guennadi
[2] https://github.com/OpenAMP/open-amp/wiki/RPMsg-Messaging-Protocol
>
> [0] https://www.spinics.net/lists/linux-virtualization/msg43799.html
> [1] https://www.spinics.net/lists/linux-virtualization/msg43802.html
next prev parent reply other threads:[~2020-09-18 11:02 UTC|newest]
Thread overview: 20+ 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
2020-09-01 17:23 ` Mathieu Poirier
2020-09-02 5:35 ` Guennadi Liakhovetski
2020-09-02 17:24 ` Mathieu Poirier
2020-09-03 5:51 ` Guennadi Liakhovetski
2020-09-03 19:27 ` Mathieu Poirier
2020-09-01 15:11 ` [PATCH v6 3/4] rpmsg: update documentation Guennadi Liakhovetski
2020-09-03 19:21 ` Mathieu Poirier
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
[not found] ` <20200917054705.GA11491@ubuntu>
2020-09-17 8:36 ` Vincent Whitchurch
2020-09-17 10:29 ` Guennadi Liakhovetski
2020-09-17 15:21 ` Arnaud POULIQUEN
[not found] ` <20200918054420.GA19246@ubuntu>
2020-09-18 7:47 ` Arnaud POULIQUEN
[not found] ` <20200918094719.GD19246@ubuntu>
2020-09-18 10:39 ` Vincent Whitchurch
2020-09-18 11:02 ` Guennadi Liakhovetski [this message]
2020-09-18 17:26 ` Arnaud POULIQUEN
2020-10-01 17:57 ` Mathieu Poirier
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=20200918110249.GE19246@ubuntu \
--to=guennadi.liakhovetski@linux.intel.com \
--cc=arnaud.pouliquen@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=jasowang@redhat.com \
--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).