public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Doug Miller <doug.miller@cornelisnetworks.com>,
	linux-remoteproc@vger.kernel.org,
	Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	OFED mailing list <linux-rdma@vger.kernel.org>
Subject: Re: Using RPMSG to communicate between host and guest drivers
Date: Mon, 26 Aug 2024 20:45:30 -0300	[thread overview]
Message-ID: <20240826234530.GK3468552@ziepe.ca> (raw)
In-Reply-To: <842aef7f-d6e1-490a-97b9-163287ddfe2d@cornelisnetworks.com>

On Mon, Aug 26, 2024 at 12:27:02PM -0400, Dennis Dalessandro wrote:
> On 7/31/24 4:02 PM, Doug Miller wrote:
> > I am working on SR-IOV support for a new adapter which has shared 
> > resources between the PF and VFs and requires an out-of-band (outside 
> > the adapter) communication mechanism to manage those resources. I have 
> > been looking at RPMSG as a mechanism to communicate between the driver 
> > on a guest (VM) and the driver on the host OS (which "owns" the 
> > resources). It appears to me that virtio is intended for communication 
> > between guests and host, and RPMSG over virtio is what I want to use.
> > 
> > Can anyone confirm that RPMSG is capable of doing what we need? If so, 
> > I'll need some help figuring out how to use that from kernel device 
> > drivers (I've not been able to find any examples of doing the 
> > service/device side). If not, is there some other facility that is 
> > better suited?
> 
> Hi Bjorn and Mathieu, any advice here for Doug? Adding linux-rdma folks as that
> is where this will eventually target.

Typically in cases like this you'd paravirtualize some of the VF
before sticking it in the VM so that there is a tidy channel between
the VF driver and the VMM to do whatever this coordination is. There
are many examples, but it is hard to see if you don't know the device
architectures in detail.

If you stick it in seperate virtio PCI device you'll have hard
problems co-ordinating the two drivers.

Jason

  parent reply	other threads:[~2024-08-26 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <133c1301-dd19-4cce-82dc-3e8ee145c594@cornelisnetworks.com>
2024-08-26 16:27 ` Using RPMSG to communicate between host and guest drivers Dennis Dalessandro
2024-08-26 16:50   ` Mathieu Poirier
2024-08-26 17:22     ` Doug Miller
2024-08-28 14:44       ` Mathieu Poirier
2024-08-28 15:34         ` Doug Miller
2024-08-26 23:45   ` Jason Gunthorpe [this message]
2024-08-28 11:49     ` Doug Miller
2024-08-28 14:17       ` Jason Gunthorpe

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=20240826234530.GK3468552@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=andersson@kernel.org \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=doug.miller@cornelisnetworks.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.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