From: Sergio Lopez <slp@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: Sergio Lopez <slp@redhat.com>
Subject: [PATCH 1/3] shared-mem: introduce page alignment restrictions
Date: Mon, 17 Feb 2025 12:52:25 +0100 [thread overview]
Message-ID: <20250217115227.4961-2-slp@redhat.com> (raw)
In-Reply-To: <20250217115227.4961-1-slp@redhat.com>
Add a subsection for page alignment restrictions and introduce the
VIRTIO_F_SHM_PAGE_SIZE feature bit.
Signed-off-by: Sergio Lopez <slp@redhat.com>
---
content.tex | 3 +++
shared-mem.tex | 7 +++++++
2 files changed, 10 insertions(+)
diff --git a/content.tex b/content.tex
index c17ffa6..575065d 100644
--- a/content.tex
+++ b/content.tex
@@ -872,6 +872,9 @@ \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
\ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits} for
handling features reserved for future use.
+ \item[VIRTIO_F_SHM_PAGE_SIZE(42)] This feature indicates that the device
+ transport provides information about the supported page size.
+
\end{description}
\drivernormative{\section}{Reserved Feature Bits}{Reserved Feature Bits}
diff --git a/shared-mem.tex b/shared-mem.tex
index 6e6f6c4..dd90cb7 100644
--- a/shared-mem.tex
+++ b/shared-mem.tex
@@ -34,6 +34,13 @@ \subsection{Addressing within regions}\label{sec:Basic Facilities of a Virtio De
The \field{shmid} may be explicit or may be inferred from the
context of the reference.
+\subsection{Page alignment restrictions}\label{sec:Basic Facilities of a Virtio Device / Shared Memory Regions / Page alignment restrictions}
+
+If VIRTIO_F_SHM_PAGE_SIZE has been negotiated, when requesting
+the device to map memory into a shared memory region, the driver
+MUST obtain the page size information from the transport and honor
+the page alignment constrains derived from that page size.
+
\devicenormative{\subsection}{Shared Memory Regions}{Basic Facilities of a Virtio
Device / Shared Memory Regions}
Shared memory regions MUST NOT expose shared memory regions which
--
2.48.1
next prev parent reply other threads:[~2025-02-17 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:52 [PATCH 0/3] shared-mem: introduce page alignment restrictions Sergio Lopez
2025-02-17 11:52 ` Sergio Lopez [this message]
2025-02-23 5:21 ` [PATCH 1/3] " Parav Pandit
2025-02-26 17:49 ` Sergio Lopez Pascual
2025-03-05 11:18 ` Parav Pandit
2025-03-05 19:08 ` Sergio Lopez Pascual
2025-03-06 3:09 ` Parav Pandit
2025-03-04 10:40 ` Michael S. Tsirkin
2025-03-04 10:52 ` Michael S. Tsirkin
2025-03-04 10:58 ` Parav Pandit
2025-03-04 12:50 ` Michael S. Tsirkin
2025-02-17 11:52 ` [PATCH 2/3] transport-pci: VIRTIO_F_SHM_PAGE_SIZE support Sergio Lopez
2025-02-17 11:52 ` [PATCH 3/3] transport-mmio: VIRTIO_F_SHM_PAGE_SIZE Sergio Lopez
2025-02-20 2:15 ` [PATCH 0/3] shared-mem: introduce page alignment restrictions Dmitry Osipenko
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=20250217115227.4961-2-slp@redhat.com \
--to=slp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox