From: Cornelia Huck <cohuck@redhat.com>
To: tstark@linux.microsoft.com, virtio-comment@lists.oasis-open.org
Cc: grahamwo@microsoft.com, benhill@microsoft.com, mst@redhat.com,
pankaj.gupta@ionos.com, tstark@microsoft.com, david@redhat.com
Subject: [virtio-comment] Re: [PATCH v2 1/1] virtio-pmem: Support describing pmem as shared memory region
Date: Tue, 27 Jul 2021 17:06:43 +0200 [thread overview]
Message-ID: <87fsvz4wzg.fsf@redhat.com> (raw)
In-Reply-To: <20210727042907.24315-2-tstark@linux.microsoft.com>
On Mon, Jul 26 2021, tstark@linux.microsoft.com wrote:
> @@ -50,12 +53,29 @@ \subsection{Device Initialization}\label{sec:Device Types / PMEM Device / Device
> File backed memory SHOULD be memory mapped to guest address space with SHARED
> memory mapping.
>
> +If VIRTIO_PMEM_F_SHMEM_REGION has been negotiated, the device MUST indicate the
> +guest physical address as a shared memory region. The device MUST use shared
> +memory region ID 0. The device SHOULD set \field{start} and \field{size} to zero.
> +
> +If VIRTIO_PMEM_F_SHMEM_REGION has not been negotiated, the device MUST indicate
> +the guest physical address as a guest absolute address. The device MUST set
> +\field{start} to the absolute address and \field{size} to the size of the
> +address range, in bytes.
> +
> \subsection{Driver Initialization}\label{sec:Device Types / PMEM Driver / Driver Initialization}
>
> Driver hotplugs the physical memory and registers associated
> region with the pmem API. Also, configures a flush callback
> function with the corresponding region.
>
> +\drivernormative{\subsubsection}{Driver Initialization}{Device Types / PMEM Driver / Driver Initialization}
> +
> +The driver SHOULD query the physical address ranges where the pmem was mapped.
Isn't the driver quite useless if it doesn't discover where the pmem can
be found? I'm not sure we need that sentence.
> +If VIRTIO_PMEM_F_SHMEM_REGION has been negotiated, the driver SHOULD query
> +shared memory ID 0 for the physical address ranges and MUST NOT use \field{start}
> +or \field{size}. Else, the driver SHOULD read the physical address ranges from
> +\field{start} and \field{size}.
'SHOULD' is probably not the right way to specify this. What about the
following:
"In order to discover the physical address ranges where the pmem was
mapped:
If VIRTIO_PMEM_F_SHMEM_REGION has been negotiated, the driver MUST query
shared memory ID 0 for the physical address ranges, and MUST NOT use
\field{start} or \field{stop}.
If VIRTIO_PMEM_F_SHMEM_REGION has not been negotiated, the driver MUST
read the physical address ranges from \field{start} and \field{stop}."
> +
> \drivernormative{\subsubsection}{Driver Initialization: Filesystem direct access}{Device Types / PMEM Driver / Driver Initialization / Direct access}
>
> Driver SHOULD enable filesystem direct access operations for
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2021-07-27 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 4:29 [PATCH v2 0/1] virtio-pmem: Support describing pmem as shared memory region tstark
2021-07-27 4:29 ` [PATCH v2 1/1] " tstark
2021-07-27 15:06 ` Cornelia Huck [this message]
2021-07-29 5:04 ` Taylor Stark
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=87fsvz4wzg.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=benhill@microsoft.com \
--cc=david@redhat.com \
--cc=grahamwo@microsoft.com \
--cc=mst@redhat.com \
--cc=pankaj.gupta@ionos.com \
--cc=tstark@linux.microsoft.com \
--cc=tstark@microsoft.com \
--cc=virtio-comment@lists.oasis-open.org \
/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.