All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [PATCH] virtio-blk: document that the capacity field can change
Date: Tue, 1 Mar 2022 07:46:23 -0500	[thread overview]
Message-ID: <20220301074608-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220301120021.147070-1-stefanha@redhat.com>

On Tue, Mar 01, 2022 at 12:00:21PM +0000, Stefan Hajnoczi wrote:
> Block devices can change size during operation. A configuration change
> notification is sent by the device and the driver detects that the field
> has changed. Document this behavior that has already been implemented in
> Linux and QEMU since 2011.
> 
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>

Acked-by: Michael S. Tsirkin <mst@redhat.com>

github issue so we can track this?

> ---
>  content.tex | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/content.tex b/content.tex
> index c6f116c..96d2aa9 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -4863,6 +4863,9 @@ \subsection{Device Operation}\label{sec:Device Types / Block Device / Device Ope
>  
>  \drivernormative{\subsubsection}{Device Operation}{Device Types / Block Device / Device Operation}
>  
> +The driver SHOULD check if the content of the \field{capacity} field has
> +changed upon receiving a configuration change notification.
> +
>  A driver MUST NOT submit a request which would cause a read or write
>  beyond \field{capacity}.
>  
> @@ -4909,6 +4912,10 @@ \subsection{Device Operation}\label{sec:Device Types / Block Device / Device Ope
>  
>  \devicenormative{\subsubsection}{Device Operation}{Device Types / Block Device / Device Operation}
>  
> +The device MAY change the content of the \field{capacity} field during
> +operation of the device. When this happens, the device SHOULD trigger a
> +configuration change notification.
> +
>  A device MUST set the \field{status} byte to VIRTIO_BLK_S_IOERR
>  for a write request if the VIRTIO_BLK_F_RO feature if offered, and MUST NOT
>  write any data.
> -- 
> 2.35.1


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2022-03-01 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 12:00 [virtio-dev] [PATCH] virtio-blk: document that the capacity field can change Stefan Hajnoczi
2022-03-01 12:46 ` Michael S. Tsirkin [this message]
2022-03-01 13:42 ` [virtio-dev] " Stefan Hajnoczi
2022-03-01 13:45   ` Michael S. Tsirkin
2022-03-01 16:37     ` Stefan Hajnoczi

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=20220301074608-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@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.