From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
sound-open-firmware@alsa-project.org,
linux-remoteproc@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Sound-open-firmware] [PATCH 5/6] vhost: add an rpmsg API
Date: Tue, 26 May 2020 15:09:19 -0500 [thread overview]
Message-ID: <f93b01b9-b14c-2433-af97-5bb9ae53f788@linux.intel.com> (raw)
In-Reply-To: <20200526185522.GA6992@ubuntu>
>>>>> +config VHOST_RPMSG
>>>>> + tristate
>>>>> + depends on VHOST
>>>>
>>>> depends on RPMSG_VIRTIO?
>>>
>>> No, RPMSG_VIRTIO is used on the guest side, VHOST_RPMSG (as well as
>>> all other vhost drivers) on the host side.
>>
>> I vaguely recalled something about sockets, and was wondering if there isn't
>> a dependency on this:
>>
>> config VHOST_VSOCK
>> tristate "vhost virtio-vsock driver"
>> depends on VSOCKETS && EVENTFD && VHOST_DPN
>> select VHOST
>
> You probably are thinking about the first patch in the series "vhost: convert
> VHOST_VSOCK_SET_RUNNING to a generic ioctl." But no, this RPMsg driver
> doesn't depend on vsock, on the contrary, it takes a (albeit tiny) piece of
> functionality from vsock and makes it global.
yes, this is what I was thinking about, thanks for clarifying.
next prev parent reply other threads:[~2020-05-26 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 10:11 [PATCH 0/6] Add a vhost RPMsg API Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 1/6] vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 2/6] vhost: (cosmetic) remove a superfluous variable initialisation Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 3/6] rpmsg: move common structures and defines to headers Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 4/6] rpmsg: update documentation Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 5/6] vhost: add an rpmsg API Guennadi Liakhovetski
2020-05-16 17:00 ` [Sound-open-firmware] " Pierre-Louis Bossart
2020-05-25 13:53 ` Guennadi Liakhovetski
2020-05-26 18:30 ` Pierre-Louis Bossart
2020-05-26 18:55 ` Guennadi Liakhovetski
2020-05-26 20:09 ` Pierre-Louis Bossart [this message]
2020-05-16 10:11 ` [PATCH 6/6] rpmsg: add a device ID to also bind to the ADSP device Guennadi Liakhovetski
2020-05-16 11:26 ` kbuild test robot
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=f93b01b9-b14c-2433-af97-5bb9ae53f788@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=sound-open-firmware@alsa-project.org \
--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).