From: Sergio Lopez <slp@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: Sergio Lopez <slp@redhat.com>
Subject: [PATCH 3/3] transport-mmio: VIRTIO_F_SHM_PAGE_SIZE
Date: Mon, 17 Feb 2025 12:52:27 +0100 [thread overview]
Message-ID: <20250217115227.4961-4-slp@redhat.com> (raw)
In-Reply-To: <20250217115227.4961-1-slp@redhat.com>
Introduce VIRTIO_F_SHM_PAGE_SIZE by adding a the new register
"SHMPageShift" to hold the value that can be used to derive the page
size value supported by the device.
Signed-off-by: Sergio Lopez <slp@redhat.com>
---
transport-mmio.tex | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/transport-mmio.tex b/transport-mmio.tex
index 94a93a1..28d1594 100644
--- a/transport-mmio.tex
+++ b/transport-mmio.tex
@@ -242,6 +242,14 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
apply to the queue selected by writing to \field{QueueSel}.
}
\hline
+ \mmioreg{SHMPageShift}{Shared memory region page shift 8 bit long}{0x0c4}{R}{%
+ If VIRTIO_F_SHM_PAGE_SIZE has been negotiated, this register returns
+ the page shift derived from the supported page size for this shared
+ memory region. The page shift is derived from the page size by using
+ this formula: $page size = 1 << (page shift + 12)$.
+ See also \ref {sec:Basic Facilities of a Virtio Device / Shared Memory Regions / Page alignment restrictions}.
+ }
+ \hline
\mmioreg{ConfigGeneration}{Configuration atomicity value}{0x0fc}{R}{
Reading from this register returns a value describing a version of the device-specific configuration space (see \field{Config}).
The driver can then access the configuration space and, when finished, read \field{ConfigGeneration} again.
--
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 ` [PATCH 1/3] " Sergio Lopez
2025-02-23 5:21 ` 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 ` Sergio Lopez [this message]
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-4-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 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.