From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sergio Lopez <slp@redhat.com>
Cc: virtio-comment@lists.linux.dev, dmitry.osipenko@collabora.com,
parav@nvidia.com
Subject: Re: [PATCH v2 1/3] shared-mem: introduce page alignment restrictions
Date: Mon, 31 Mar 2025 12:16:11 -0400 [thread overview]
Message-ID: <20250331121538-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250331150548.50595-2-slp@redhat.com>
On Mon, Mar 31, 2025 at 11:05:46AM -0400, Sergio Lopez wrote:
> Add a subsection for page alignment restrictions.
>
> Signed-off-by: Sergio Lopez <slp@redhat.com>
> ---
> shared-mem.tex | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/shared-mem.tex b/shared-mem.tex
> index 6e6f6c4..2021083 100644
> --- a/shared-mem.tex
> +++ b/shared-mem.tex
> @@ -34,6 +34,12 @@ \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}
> +
> +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.
> +
will make existing drivers autmatically incompliant with new devices.
we generally avoid things like this.
> \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.49.0
next prev parent reply other threads:[~2025-03-31 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 15:05 [PATCH v2 0/3] shared-mem: introduce page alignment restrictions Sergio Lopez
2025-03-31 15:05 ` [PATCH v2 1/3] " Sergio Lopez
2025-03-31 16:16 ` Michael S. Tsirkin [this message]
2025-03-31 16:40 ` Sergio Lopez Pascual
2025-04-01 9:14 ` Michael S. Tsirkin
2025-04-01 9:22 ` Parav Pandit
2025-04-01 9:33 ` Sergio Lopez Pascual
2025-04-01 9:37 ` Parav Pandit
2025-04-01 10:18 ` Michael S. Tsirkin
2025-04-02 9:04 ` Parav Pandit
2025-04-01 9:26 ` Sergio Lopez Pascual
2025-04-01 10:09 ` Michael S. Tsirkin
2025-04-01 10:46 ` Sergio Lopez Pascual
2025-03-31 15:05 ` [PATCH v2 2/3] transport-pci: introduce page_shift field for SHM Sergio Lopez
2025-03-31 15:05 ` [PATCH v2 3/3] transport-mmio: introduce SHMPageShift register Sergio Lopez
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=20250331121538-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=parav@nvidia.com \
--cc=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