[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqJn2XtvWaDBSqYPUe2ZVxE7t4EbAt8OPncbQaKjh1jY5w@mail.gmail.com>
Date: Wed, 30 Jul 2025 08:39:44 -0500
From: Rob Herring <robh@...nel.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: linux-kernel@...r.kernel.org, Eugenio Pérez <eperezma@...hat.com>,
Jason Wang <jasowang@...hat.com>, "Michael S. Tsirkin" <mst@...hat.com>,
Saravana Kannan <saravanak@...gle.com>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
Arnd Bergmann <arnd@...nel.org>, Vincent Guittot <vincent.guittot@...aro.org>,
Alex Bennée <alex.bennee@...aro.org>,
Bill Mills <bill.mills@...aro.org>, devicetree@...r.kernel.org,
virtualization@...ts.linux.dev, Sudeep Holla <sudeep.holla@....com>,
Bertrand Marquis <bertrand.marquis@....com>, "Edgar E . Iglesias" <edgar.iglesias@....com>,
Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Subject: Re: [RFC PATCH 0/6] virtio: Add support for Virtio message transport
On Wed, Jul 30, 2025 at 4:29 AM Viresh Kumar <viresh.kumar@...aro.org> wrote:
>
> Hello,
>
> This RFC series introduces support for a new Virtio transport type:
> "virtio-msg", as proposed in [1]. Unlike existing transport types like
> virtio-mmio or virtio-pci, which rely on memory-mapped registers, virtio-msg
> implements transport operations via structured messages. Those messages can be
> transported through different mechanisms such as mailboxes, shared memory based
> FIFO or specific protocols such as FF-A on Arm.
>
> This series includes:
> - Core virtio-msg transport support.
> - Two message transport bus implementations:
> - virtio-msg-ffa: based on ARM's Firmware Framework for Arm (FF-A).
> - virtio-msg-loopback: a loopback device for testing and validation.
>
> The code is available here for reference: [2] and virtio-msg loopback and FF-A
> test setups are explained here: [3] and [4].
>
> This series is based on v6.16 and depends on commit [5].
>
>
> ### Memory Mapping and Reserved Memory Usage
>
> The first two patches enhance the reserved-memory subsystem to support attaching
> struct device`s that do not originate from DT nodes — essential for virtual or
> dynamically discovered devices like the FF-A or loopback buses.
We support creating devices from reserved-memory nodes. Just add a
compatible which you should do anyways because node names are not
supposed to be that specific or an ABI.
Rob
Powered by blists - more mailing lists