From: "Michael S. Tsirkin" <mst@redhat.com>
To: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
Cc: kvm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
virtualization@lists.linux-foundation.org,
sound-open-firmware@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Jason Wang <jasowang@redhat.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: Re: [PATCH v4 0/4] Add a vhost RPMsg API
Date: Tue, 4 Aug 2020 10:10:23 -0400 [thread overview]
Message-ID: <20200804100747-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200804131918.GA19025@ubuntu>
On Tue, Aug 04, 2020 at 03:19:19PM +0200, Guennadi Liakhovetski wrote:
> Hi Michael,
>
> On Tue, Aug 04, 2020 at 08:26:53AM -0400, Michael S. Tsirkin wrote:
> > On Wed, Jul 22, 2020 at 05:09:23PM +0200, Guennadi Liakhovetski wrote:
> > > Hi,
> > >
> > > Now that virtio-rpmsg endianness fixes have been merged we can
> > > proceed with the next step.
> >
> > OK my attempts to resolve conflicts just created a mess.
>
> You just need to apply my previous patch for virtio-rpmsg first
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/rpmsg/virtio_rpmsg_bus.c?id=111d1089700cdb752681ef44f54ab6137736f5c2
> Then this series should apply cleanly.
>
> Thanks
> Guennadi
Hmm. Could you test the vhost branch in my tree, and tell me if that looks
good to you?
> > I dropped these for now, could you pls rebase on top
> > of linux-next branch in my tree, and repost?
> > Thanks!
> >
> >
> > > 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
> > >
> > > 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 | 375 +++++++++++++++++++++++++++++++
> > > drivers/vhost/vhost_rpmsg.h | 74 ++++++
> > > include/linux/virtio_rpmsg.h | 83 +++++++
> > > include/uapi/linux/rpmsg.h | 3 +
> > > include/uapi/linux/vhost.h | 4 +-
> > > 9 files changed, 553 insertions(+), 80 deletions(-)
> > > create mode 100644 drivers/vhost/rpmsg.c
> > > create mode 100644 drivers/vhost/vhost_rpmsg.h
> > > create mode 100644 include/linux/virtio_rpmsg.h
> > >
> > > --
> > > 2.27.0
> >
next prev parent reply other threads:[~2020-08-04 14:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 15:09 [PATCH v4 0/4] Add a vhost RPMsg API Guennadi Liakhovetski
2020-07-22 15:09 ` [PATCH v4 1/4] vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl Guennadi Liakhovetski
2020-07-23 8:34 ` Stefano Garzarella
2020-07-22 15:09 ` [PATCH v4 2/4] rpmsg: move common structures and defines to headers Guennadi Liakhovetski
2020-08-11 17:51 ` Mathieu Poirier
2020-07-22 15:09 ` [PATCH v4 3/4] rpmsg: update documentation Guennadi Liakhovetski
2020-07-22 15:09 ` [PATCH v4 4/4] vhost: add an RPMsg API Guennadi Liakhovetski
2020-08-04 14:27 ` Michael S. Tsirkin
2020-08-04 15:19 ` Guennadi Liakhovetski
2020-08-10 13:44 ` Michael S. Tsirkin
2020-08-12 12:32 ` Guennadi Liakhovetski
2020-08-25 13:41 ` Guennadi Liakhovetski
2020-08-25 13:53 ` Michael S. Tsirkin
2020-07-30 16:08 ` [PATCH v4 0/4] Add a vhost " Michael S. Tsirkin
2020-07-31 5:47 ` Guennadi Liakhovetski
2020-08-03 13:25 ` Mathieu Poirier
2020-08-03 20:46 ` Michael S. Tsirkin
2020-08-04 13:37 ` Mathieu Poirier
2020-08-04 14:07 ` Michael S. Tsirkin
2020-08-04 19:30 ` Mathieu Poirier
2020-08-05 11:34 ` Michael S. Tsirkin
2020-08-04 12:26 ` Michael S. Tsirkin
2020-08-04 13:19 ` Guennadi Liakhovetski
2020-08-04 14:10 ` Michael S. Tsirkin [this message]
2020-08-04 14:46 ` Guennadi Liakhovetski
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=20200804100747-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bjorn.andersson@linaro.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--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=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).