From: Sergio Lopez <slp@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: mst@redhat.com, dmitry.osipenko@collabora.com, parav@nvidia.com,
Sergio Lopez <slp@redhat.com>
Subject: [PATCH v3 3/3] transport-mmio: introduce SHMPageShift register
Date: Mon, 31 Mar 2025 17:37:11 -0400 [thread overview]
Message-ID: <20250331213711.63398-4-slp@redhat.com> (raw)
In-Reply-To: <20250331213711.63398-1-slp@redhat.com>
Introduce the "SHMPageShift" register which, when read, returns the
page shift value that can be used to derive the page size value
supported by the shared memory regions in 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..042a82c 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}{%
+ Reading from this register returns the page shift derived from the supported
+ page size for the memory region selected by the \field{SHMSel} register. 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.49.0
next prev parent reply other threads:[~2025-04-01 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 21:37 [PATCH v3 0/3] shared-mem: introduce page alignment restrictions Sergio Lopez
2025-03-31 21:37 ` [PATCH v3 1/3] " Sergio Lopez
2025-04-01 16:42 ` Daniel Verkamp
2025-04-02 7:32 ` Michael S. Tsirkin
2025-03-31 21:37 ` [PATCH v3 2/3] transport-pci: introduce page_shift field for SHM Sergio Lopez
2025-03-31 21:37 ` Sergio Lopez [this message]
2025-04-02 7:37 ` [PATCH v3 0/3] shared-mem: introduce page alignment restrictions Michael S. Tsirkin
2025-04-02 9:18 ` Sergio Lopez Pascual
2025-04-02 9:55 ` Parav Pandit
2025-04-02 12:22 ` Sergio Lopez Pascual
2025-04-02 12:36 ` Parav Pandit
2025-04-02 14:49 ` Michael S. Tsirkin
2025-04-02 16:28 ` Sergio Lopez Pascual
2025-04-02 8:54 ` Parav Pandit
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=20250331213711.63398-4-slp@redhat.com \
--to=slp@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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