From: Cornelia Huck <cohuck@redhat.com>
To: tstark@linux.microsoft.com, virtio-comment@lists.oasis-open.org
Cc: grahamwo@microsoft.com, benhill@microsoft.com,
tstark@microsoft.com, pankaj.gupta.linux@gmail.com
Subject: Re: [virtio-comment] [PATCH v4 1/1] virtio-pmem: Support describing pmem as shared memory region
Date: Mon, 08 Nov 2021 13:54:27 +0100 [thread overview]
Message-ID: <87wnlivmd8.fsf@redhat.com> (raw)
In-Reply-To: <20211105201105.2977-2-tstark@linux.microsoft.com>
On Fri, Nov 05 2021, tstark@linux.microsoft.com wrote:
> From: Taylor Stark <tstark@microsoft.com>
>
> Update the virtio-pmem spec to add support for describing the pmem region as a
> shared memory window. This is required to support virtio-pmem in Hyper-V, since
> Hyper-V only allows PCI devices to operate on memory ranges defined via BARs.
> When using the virtio PCI transport, shared memory regions are described via
> PCI BARs.
>
> Signed-off-by: Taylor Stark <tstark@microsoft.com>
> ---
> conformance.tex | 14 ++++++++++++--
> virtio-pmem.tex | 34 +++++++++++++++++++++++++++++-----
> 2 files changed, 41 insertions(+), 7 deletions(-)
(...)
> @@ -41,17 +44,38 @@ \subsection{Device configuration layout}\label{sec:Device Types / PMEM Device /
> \item[\field{size}] contains the length of this address range.
> \end{description}
I wonder whether we should also amend the description of the config
space fields to "contains (...), if VIRTIO_PMEM_F_SHMEM_REGION has not
been negotiated". But maybe that is not really needed.
>
> +\subsection{Device Initialization}\label{sec:Device Types / PMEM Device / Device Initialization}
> +
> +The device indicates the guest physical address to the driver in one of two ways:
> \begin{enumerate}
> -\item Driver vpmem start is read from \field{start}.
> -\item Driver vpmem end is read from \field{size}.
> +\item As a guest absolute address, using virtio_pmem_config.
> +\item As a shared memory region.
> \end{enumerate}
Otherwise, looks good to me.
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-11-08 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 20:11 [virtio-comment] [PATCH v4 0/1] virtio-pmem: Support describing pmem as shared memory region tstark
2021-11-05 20:11 ` [virtio-comment] [PATCH v4 1/1] " tstark
2021-11-08 12:54 ` Cornelia Huck [this message]
2021-11-10 18:53 ` 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=87wnlivmd8.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=benhill@microsoft.com \
--cc=grahamwo@microsoft.com \
--cc=pankaj.gupta.linux@gmail.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.