All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@amd.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	<qemu-devel@nongnu.org>, <alex.bennee@linaro.org>,
	<bill.mills@linaro.org>
Subject: Re: [PATCH v1 0/5] virtio: Add the virtio-msg transport
Date: Tue, 3 Feb 2026 18:09:46 +0100	[thread overview]
Message-ID: <aYIr2rAPuXJJ-spR@zapote> (raw)
In-Reply-To: <20260203082120-mutt-send-email-mst@kernel.org>

On Tue, Feb 03, 2026 at 08:22:38AM -0500, Michael S. Tsirkin wrote:
> On Tue, Oct 28, 2025 at 04:23:45PM +0100, Edgar E. Iglesias wrote:
> > From: "Edgar E. Iglesias" <edgar.iglesias@amd.com>
> > 
> > This adds virtio-msg, a new virtio transport. Virtio-msg works by
> > exchanging messages over a bus and doesn't rely on trapping and emulation
> > making it a good fit for a number of applications such as AMP, real-time
> > and safety applications.
> > 
> > Together with the new transport, this series adds a PCI device that
> > implements an AMP setup much like it could look if two SoC's would
> > use virtio-msg across a PCI link.
> > 
> > Current gaps and limitations:
> > Shared memory FIFO layout likely to change in the future.
> > Temporarily uses PCI Vendor Xilinx / Device 0x9039.
> > Documentation.
> 
> 
> I'm happy that the spec effort is making progress finally.
> Do you want to repost a version aligned to the latest spec posted?
> 
>

Thanks Michael, Yes, I'll repost a new version soon aligned with the
latest spec and addressing comments from Alex.

Cheers,
Edgar


      reply	other threads:[~2026-02-03 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 15:23 [PATCH v1 0/5] virtio: Add the virtio-msg transport Edgar E. Iglesias
2025-10-28 15:23 ` [PATCH v1 1/5] virtio: Introduce notify_queue Edgar E. Iglesias
2025-11-05 12:38   ` Alex Bennée
2025-11-13 20:43     ` Edgar E. Iglesias
2025-10-28 15:23 ` [PATCH v1 2/5] virtio: Add virtio_queue_get_rings Edgar E. Iglesias
2025-11-05 12:39   ` Alex Bennée
2025-10-28 15:23 ` [PATCH v1 3/5] virtio: Add the virtio-msg transport Edgar E. Iglesias
2025-10-28 15:23 ` [PATCH v1 4/5] hw/misc: Add generic virtio-msg AMP PCI device Edgar E. Iglesias
2025-10-28 15:23 ` [PATCH v1 5/5] docs: Describe virtio-msg-amp-pci Edgar E. Iglesias
2025-11-05 19:52   ` Alex Bennée
2025-10-28 15:30 ` [PATCH v1 0/5] virtio: Add the virtio-msg transport Edgar E. Iglesias
2026-02-03 13:22 ` Michael S. Tsirkin
2026-02-03 17:09   ` Edgar E. Iglesias [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=aYIr2rAPuXJJ-spR@zapote \
    --to=edgar.iglesias@amd.com \
    --cc=alex.bennee@linaro.org \
    --cc=bill.mills@linaro.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.