All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org, qemu-block@nongnu.org,
	qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Max Reitz <mreitz@redhat.com>,
	Paul Durrant <paul.durrant@citrix.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Anthony Perard <anthony.perard@citrix.com>
Subject: [PATCH v2 0/2] xen-block: fix sector size confusion
Date: Wed, 27 Mar 2019 17:32:04 +0000	[thread overview]
Message-ID: <20190327173206.9065-1-paul.durrant@citrix.com> (raw)

The Xen blkif protocol is confusing but discussion with the maintainer
has clarified that sector based quantities in requests and the 'sectors'
value advertized in xenstore should always be in terms of 512-byte
units and not the advertised logical 'sector-size' value.

This series fixes xen-block to adhere to the spec.

Paul Durrant (2):
  xen-block: scale sector based quantities correctly
  xen-block: always report 'sectors' in terms of 512-byte units

 hw/block/dataplane/xen-block.c | 28 +++++++++++++---------------
 hw/block/xen-block.c           |  2 +-
 hw/block/xen_blkif.h           |  2 ++
 3 files changed, 16 insertions(+), 16 deletions(-)
---
v2:
 - Split up previous single patch

Cc: Anthony Perard <anthony.perard@citrix.com>
Cc: Kevin Wolf <kwolf@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>
-- 
2.20.1.2.gb21ebb6


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-03-27 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 17:32 Paul Durrant [this message]
2019-03-27 17:32 ` [PATCH v2 1/2] xen-block: scale sector based quantities correctly Paul Durrant
2019-03-27 17:32 ` [PATCH v2 2/2] xen-block: always report 'sectors' in terms of 512-byte units Paul Durrant
2019-03-27 18:20 ` [PATCH v2 0/2] xen-block: fix sector size confusion Andrew Cooper
     [not found] ` <3585a316-6349-b89e-99be-799b055594db@citrix.com>
2019-03-27 20:32   ` Paul Durrant
     [not found]   ` <f9a7e4fa5b794cf88593a86923142a87@AMSPEX02CL02.citrite.net>
2019-03-28 11:40     ` Anthony PERARD
     [not found]     ` <20190328114012.GG1420@perard.uk.xensource.com>
2019-03-28 11:46       ` Andrew Cooper
     [not found]       ` <28bfdf32-916f-fb55-e2ab-13871b5e0fdd@citrix.com>
2019-03-28 11:56         ` Kevin Wolf
2019-04-01  8:54         ` [Qemu-devel] [Xen-devel] " Paul Durrant
2019-04-01  8:54         ` Paul Durrant
     [not found]         ` <20190328115619.GC4857@localhost.localdomain>
2019-04-01  9:01           ` Paul Durrant
2019-04-01  9:01             ` [Qemu-devel] [Xen-devel] " Paul Durrant
2019-04-01  9:34             ` Kevin Wolf
2019-04-01  9:34               ` [Qemu-devel] [Xen-devel] " Kevin Wolf
2019-04-01  9:48               ` Paul Durrant
2019-04-01  9:48               ` [Qemu-devel] [Xen-devel] " Paul Durrant
2019-04-01 19:37               ` Håkon Alstadheim

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=20190327173206.9065-1-paul.durrant@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=stefanha@redhat.com \
    --cc=xen-devel@lists.xenproject.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.