All of lore.kernel.org
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: tstark@linux.microsoft.com
Cc: virtio-comment@lists.oasis-open.org, grahamwo@microsoft.com,
	benhill@microsoft.com, tstark@microsoft.com,
	pankaj.gupta.linux@gmail.com, Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [virtio-comment] [PATCH v5 1/1] virtio-pmem: Support describing pmem as shared memory region
Date: Thu, 18 Nov 2021 18:37:52 +0100	[thread overview]
Message-ID: <20211118183752.32100dc3.pasic@linux.ibm.com> (raw)
In-Reply-To: <20211110185555.190-2-tstark@linux.microsoft.com>

On Wed, 10 Nov 2021 10:55:55 -0800
tstark@linux.microsoft.com wrote:
[..]
> @@ -36,22 +39,45 @@ \subsection{Device configuration layout}\label{sec:Device Types / PMEM Device /
>  \end{lstlisting}
>  
>  \begin{description}
> -\item[\field{start}] contains the physical address of the first byte of the persistent memory region.
> +\item[\field{start}] contains the physical address of the first byte of the
> +persistent memory region, if VIRTIO_PMEM_F_SHMEM_REGION has not been negotiated.
>  
> -\item[\field{size}] contains the length of this address range.
> +\item[\field{size}] contains the length of this address range, if
> +VIRTIO_PMEM_F_SHMEM_REGION has not been negotiated.
>  \end{description}
>  
> +\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}
>  
> -\subsection{Driver Initialization}\label{sec:Device Types / PMEM Driver / Driver Initialization}
> -
>  The driver determines the start address and size of the persistent memory region in preparation for reading or writing data.
>  
>  The driver initializes req_vq in preparation for making flush requests.
>  
> +\devicenormative{\subsubsection}{Device Initialization}{Device Types / PMEM Device / Device Initialization}
> +
> +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.

Sorry for joining in this late. 

I'm wondering if the quoted parts implies that the device SHOULD change
its config space (fields start and size) when the driver sets
FEATURES_OK, and the feature is VIRTIO_PMEM_F_SHMEM_REGION set at the
device (it was offered, and got set).

My train of thought is: initially no feature is considered negotiated,
and config space access is allowed before feature negotiation is
completed. That means the at this stage the device must indicate via
the config space, and thus \field{size} != 0. But as a part of the
transition 'features not negotiated' -> 'features negotiated' the device
needs to go '\field{size} != 0' -> '\field{size} == 0'

Is that what we want?

Also I understand that Hyper-V would make the device cease operation if
the feature VIRTIO_PMEM_F_SHMEM_REGION was not accepted by the driver.
I believe I've read that in some previous email.

Do we need a  'MAY fail to operate further if' statement? Anything that
ain't guarded by feature bits ain't optional, and anything that is
guarded by feature bits is optional unless explicitly stated otherwise.

Regards,
Halil

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/


  parent reply	other threads:[~2021-11-18 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 18:55 [virtio-comment] [PATCH v5 0/1] virtio-pmem: Support describing pmem as shared memory region tstark
2021-11-10 18:55 ` [virtio-comment] [PATCH v5 1/1] " tstark
2021-11-11 10:52   ` Cornelia Huck
2021-11-11 18:17     ` Taylor Stark
2021-11-23 16:42     ` Stefan Hajnoczi
2021-11-23 16:49       ` Cornelia Huck
2021-11-24 15:36         ` Stefan Hajnoczi
2021-11-16  0:31   ` [virtio-comment] " Pankaj Gupta
2021-11-18 17:37   ` Halil Pasic [this message]
2021-11-21  8:08     ` [virtio-comment] " Taylor Stark
2021-11-22 11:58       ` Cornelia Huck
2021-11-22 19:56         ` Halil Pasic
2021-11-23 11:10           ` Cornelia Huck

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=20211118183752.32100dc3.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.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.