public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: dverkamp@chromium.org, mst@redhat.com,
	virtualization@lists.linux-foundation.org,
	virtio-dev@lists.linux.dev, oren@nvidia.com, parav@nvidia.com
Subject: Re: [PATCH v2 1/1] virtio-blk: Add description for blk_size field
Date: Wed, 9 Oct 2024 11:10:24 -0400	[thread overview]
Message-ID: <20241009151024.GB45445@fedora.redhat.com> (raw)
In-Reply-To: <1389ad0b-89b0-4e50-b07d-02bd6141fc7d@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

On Wed, Oct 09, 2024 at 01:46:17AM +0300, Max Gurtovoy wrote:
> 
> On 08/10/2024 23:15, Stefan Hajnoczi wrote:
> > On Sun, Oct 06, 2024 at 07:56:09PM +0300, Max Gurtovoy wrote:
> > > This field is only valid when the VIRTIO_BLK_F_BLK_SIZE feature bit is
> > > offered by the device.
> > > 
> > > The blk_size field actually represents the logical block size of the
> > > device. It is always a power of two and typically ranges from 512 bytes
> > > to larger values such as 4 KB.
> > > 
> > > Add description for this field to provide clarity on its constraints.
> > > 
> > > Signed-off-by: Max Gurtovoy<mgurtovoy@nvidia.com>
> > > ---
> > > 
> > > changes from V1:
> > >   - Addressed Stefan's and Daniel's comments:
> > >         1. use SHOULD instead of MUST
> > >         2. Add a note that devices may return IOERR upon misaligned IO
> > >   - Add a note that devices may return IOERR if IO size is not following
> > >     the block size granularity.
> > > ---
> > >   device-types/blk/description.tex | 34 ++++++++++++++++++++++++++++++++
> > >   1 file changed, 34 insertions(+)
> > Reviewed-by: Stefan Hajnoczi<stefanha@redhat.com>
> 
> I'll add both yours and Daniel's Reviewed-by signatures and fix a small
> comment from Daniel.
> 
> Can you please remind me the next step I should do ?
> 
> Should I open an issue at the oasis github and mention it as "Fixes: " in
> the commit message ?

The GitHub repo is here:
https://github.com/oasis-tcs/virtio-spec

The instructions for requesting a vote on a spec patch are:

  To request a TC vote on resolving a specific comment:

  1. Create a github issue, or edit an existing issue, with a short summary of the comment. The issue MUST specify the link to the latest proposal in the TC mailing list archives. Note: the link MUST be in the issue description itself - not in the comments.
  2. Reply by email to the comment email, requesting that the TC vote on resolving the issue. The mail requesting the vote should include the following, on a line by itself:

    Fixes: https://github.com/oasis-tcs/virtio-spec/issues/NNN
    (NNN is the issue number)
  3. Please make sure to allow time for review between posting a comment and asking for a vote.

Thanks,
Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2024-10-09 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 16:56 [PATCH v2 1/1] virtio-blk: Add description for blk_size field Max Gurtovoy
2024-10-08  2:14 ` Daniel Verkamp
2024-10-08 20:15 ` Stefan Hajnoczi
2024-10-08 22:46   ` Max Gurtovoy
2024-10-09 15:10     ` Stefan Hajnoczi [this message]

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=20241009151024.GB45445@fedora.redhat.com \
    --to=stefanha@redhat.com \
    --cc=dverkamp@chromium.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@redhat.com \
    --cc=oren@nvidia.com \
    --cc=parav@nvidia.com \
    --cc=virtio-dev@lists.linux.dev \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox