From: Jason Gunthorpe <jgg@ziepe.ca>
To: Doug Miller <doug.miller@cornelisnetworks.com>
Cc: Dennis Dalessandro <dennis.dalessandro@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: Wed, 28 Aug 2024 11:17:08 -0300 [thread overview]
Message-ID: <20240828141708.GQ3468552@ziepe.ca> (raw)
In-Reply-To: <0f6e27d3-8942-492e-86e8-730c00a5aa37@cornelisnetworks.com>
On Wed, Aug 28, 2024 at 06:49:27AM -0500, Doug Miller wrote:
> > 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.
>
> Can you give more detail on how this paravirtualization is accomplished?
> Or point to an example?
Not sure I have easy examples, several devices I've seen proxy things
through their FW/HW. I think some of the Intel NICs were working like
this.
Some have full vfio-mdevs or qemu modules to intercept registers and
build it.
> It seems to me that rpmsg would be a cleaner solution, at least
> until I can see how paravirtualization is implemented for
> comparison.
I think you will find it very hard to connect such a thing up
throughout all the peices of software. Having two related devices
across everything is not easy.
Jason
prev parent reply other threads:[~2024-08-28 14:17 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
2024-08-28 11:49 ` Doug Miller
2024-08-28 14:17 ` Jason Gunthorpe [this message]
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=20240828141708.GQ3468552@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