public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Doug Miller <doug.miller@cornelisnetworks.com>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-remoteproc@vger.kernel.org,
	OFED mailing list <linux-rdma@vger.kernel.org>,
	"Dalessandro, Dennis" <dennis.dalessandro@cornelisnetworks.com>
Subject: Re: How to create/use RPMSG-over-VIRTIO devices in Linux
Date: Sun, 15 Sep 2024 13:58:00 -0300	[thread overview]
Message-ID: <20240915165800.GF869260@ziepe.ca> (raw)
In-Reply-To: <CANLsYkw-5i_4=UXwtG_SfR7rkjKEz3ieSOP2s4SOCozkWMct7w@mail.gmail.com>

On Fri, Sep 13, 2024 at 08:39:26AM -0600, Mathieu Poirier wrote:
> KVM has nothing to do with this.  The life of a virtio device starts
> in the VMM (Virtual Machine Manager) where a backend device is created
> and a virtio MMIO entry for that device is added to the device tree
> that is fed to the VM kernel.  When the VM kernel boots the virtio
> MMIO entry in the DT is parsed as part of the normal device discovery
> process and a virtio-device is instantiated, added to the virtio-bus
> and a driver is probed.
> 
> I suggest you start looking at that process using the kvmtool and a
> simple virtio device such as virtio-rng.

I would repeat again, I think trying to create a companion virtio
device to go along with a real vPCI device and then logically
associating both of them with a single driver is going to cause so
much pain you should not do it.

Find a way to send your RPCs through your own vPCI device.

Jason

  reply	other threads:[~2024-09-15 16:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 15:52 How to create/use RPMSG-over-VIRTIO devices in Linux Doug Miller
2024-09-10 13:12 ` Doug Miller
2024-09-10 15:13   ` Mathieu Poirier
2024-09-10 15:43     ` Doug Miller
2024-09-11 16:12       ` Mathieu Poirier
2024-09-11 17:24         ` Doug Miller
2024-09-12 15:10           ` Mathieu Poirier
2024-09-13 11:46             ` Doug Miller
2024-09-13 14:39               ` Mathieu Poirier
2024-09-15 16:58                 ` Jason Gunthorpe [this message]
2024-09-16 13:38                   ` Doug Miller
2024-09-20 12:45                     ` Jason Gunthorpe
2024-09-20 13:56                       ` Doug Miller
2024-09-23 13:39                         ` Jason Gunthorpe
2024-09-17 21:35                 ` 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=20240915165800.GF869260@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