qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Doug Miller <doug.miller@cornelisnetworks.com>
To: qemu-devel@nongnu.org, virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: "Dalessandro, Dennis" <dennis.dalessandro@cornelisnetworks.com>
Subject: Looking for help and advice on using RPMSG-over-VIRTIO
Date: Thu, 19 Sep 2024 07:26:33 -0500	[thread overview]
Message-ID: <8da76a79-444b-46f4-96db-309d03689220@cornelisnetworks.com> (raw)

I am working on adding SR-IOV for a new adapter and need to find a way
to communicate between guest and host drivers without using the adapter
hardware. I have been looking at RPMSG-over-VIRTIO as a way to this, but
have not been able to figure out how the host would setup the RPMSG
device needed for this.

I have seen at least one bug in virtio_rpmsg_bus that was discovered and
fixed by qemu developers, and so am hoping there may be some experience
with rpmsg here that can help.

I see an example in the Linux kernel for using rpmsg from the guest
(client) side, in samples/rpmsg/rpmsg_client_sample.c. What I'm having
difficulty with is finding examples or documentation on how to do the
host side. I have heard that the VMMs may also play a role in setting
this up, or are doing something similar, but so far I am not able to
find code examples in qemu or libvert.

Any help would be appreciated,
Doug

External recipient


             reply	other threads:[~2024-09-19 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 12:26 Doug Miller [this message]
2024-09-30 17:33 ` Looking for help and advice on using RPMSG-over-VIRTIO Doug Miller

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=8da76a79-444b-46f4-96db-309d03689220@cornelisnetworks.com \
    --to=doug.miller@cornelisnetworks.com \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtualization@lists.linux.dev \
    /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).