All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Alexander Graf <graf@amazon.com>
Cc: virtio-comment@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH] Add VIRTIO_F_DMB (Device Memory Buffer)
Date: Thu, 16 Jul 2026 10:50:25 +0100	[thread overview]
Message-ID: <20260716095025.GB741667@fedora> (raw)
In-Reply-To: <20260702040006.65669-1-graf@amazon.com>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Thu, Jul 02, 2026 at 04:00:06AM +0000, Alexander Graf wrote:
> * Shared memory region id: DMB needs a well-known shmid so the driver can
>   locate the region independent of device type. This draft reserves shmid 2
>   and adds a "Reserved Shared Memory Region IDs" registry. However shmid is
>   currently a per-device-type namespace, and at least one device type
>   (virtio-scmi) documents the entire shmid space as its own. Guidance
>   requested on the preferred mechanism: (a) a small transport-reserved shmid
>   range with device types adjusted to exclude it, or (b) identifying the DMB
>   region by a means other than a fixed shmid. The exact number is not fixed
>   pending this decision.

Hi Alex,
VIRTIO Transports could provide a way to fetch the DMB shmid. For
example, the MMIO transport would get a new read-only DMBSHMId register
that contains a valid shmid when VIRTIO_F_DMB has been negotiated.

Allowing the device to report an arbitrary shmid is flexible - it won't
interfere with device-specific Shared Memory Regions or future
Transport-specific Shared Memory Regions.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-07-16 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  4:00 [PATCH] Add VIRTIO_F_DMB (Device Memory Buffer) Alexander Graf
2026-07-16  9:50 ` Stefan Hajnoczi [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=20260716095025.GB741667@fedora \
    --to=stefanha@redhat.com \
    --cc=graf@amazon.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@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 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.