From: Paul Durrant <Paul.Durrant@citrix.com> To: Anthony Perard <anthony.perard@citrix.com> Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, "qemu-block@nongnu.org" <qemu-block@nongnu.org>, Stefano Stabellini <sstabellini@kernel.org>, Stefan Hajnoczi <stefanha@redhat.com>, Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com> Subject: Re: [Qemu-devel] [PATCH] xen-block: support feature-large-sector-size Date: Wed, 10 Apr 2019 15:55:24 +0000 [thread overview] Message-ID: <f76a3a96fabc4afbb96586a9b5fe682f@AMSPEX02CL01.citrite.net> (raw) In-Reply-To: <20190410155217.GH1435@perard.uk.xensource.com> > -----Original Message----- > From: Anthony PERARD [mailto:anthony.perard@citrix.com] > Sent: 10 April 2019 16:52 > To: Paul Durrant <Paul.Durrant@citrix.com> > Cc: qemu-devel@nongnu.org; xen-devel@lists.xenproject.org; qemu-block@nongnu.org; Stefano Stabellini > <sstabellini@kernel.org>; Stefan Hajnoczi <stefanha@redhat.com>; Kevin Wolf <kwolf@redhat.com>; Max > Reitz <mreitz@redhat.com> > Subject: Re: [PATCH] xen-block: support feature-large-sector-size > > On Tue, Apr 09, 2019 at 05:40:38PM +0100, Paul Durrant wrote: > > A recent Xen commit [1] clarified the semantics of sector based quantities > > used in the blkif protocol such that it is now safe to create a xen-block > > device with a logical_block_size != 512, as long as the device only > > connects to a frontend advertizing 'feature-large-block-size'. > > > > This patch modifies xen-block accordingly. It also uses a stack variable > > for the BlockBackend in xen_block_realize() to avoid repeated dereferencing > > of the BlockConf pointer, and changes the parameters of > > xen_block_dataplane_create() so that the BlockBackend pointer and sector > > size are passed expicitly rather than implicitly via the BlockConf. > > > > These modifications have been tested against a recent Windows PV XENVBD > > driver [2] using a xen-disk device with a 4kB logical block size. > > > > [1] http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=67e1c050e36b2c9900cca83618e56189effbad98 > > [2] https://winpvdrvbuild.xenproject.org:8080/job/XENVBD-master/126 > > > > Signed-off-by: Paul Durrant <paul.durrant@citrix.com> > > --- > > diff --git a/hw/block/xen-block.c b/hw/block/xen-block.c > > index ef635be4c2..05e890ad78 100644 > > --- a/hw/block/xen-block.c > > +++ b/hw/block/xen-block.c > > @@ -51,11 +51,25 @@ static void xen_block_connect(XenDevice *xendev, Error **errp) > [...] > > + if (xen_device_frontend_scanf(xendev, "feature-large-sector-size", "%u", > > + &feature_large_sector_size) != 1) { > > + feature_large_sector_size = 0; > > + } > > + > > + if (feature_large_sector_size != 1 && > > + conf->logical_block_size != XEN_BLKIF_SECTOR_SIZE) { > > + error_setg(errp, "logical_block_size != %u not supported", > > Maybe add "by frontend" to the error message? Yes, I'm fine with that addition. > > > + XEN_BLKIF_SECTOR_SIZE); > > + return; > > + } > > + > > With the question answered: > Reviewed-by: Anthony PERARD <anthony.perard@citrix.com> > Thanks, Paul > Thanks, > > -- > Anthony PERARD
WARNING: multiple messages have this Message-ID (diff)
From: Paul Durrant <Paul.Durrant@citrix.com> To: Anthony Perard <anthony.perard@citrix.com> Cc: Kevin Wolf <kwolf@redhat.com>, Stefano Stabellini <sstabellini@kernel.org>, "qemu-block@nongnu.org" <qemu-block@nongnu.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Max Reitz <mreitz@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org> Subject: Re: [Qemu-devel] [PATCH] xen-block: support feature-large-sector-size Date: Wed, 10 Apr 2019 15:55:24 +0000 [thread overview] Message-ID: <f76a3a96fabc4afbb96586a9b5fe682f@AMSPEX02CL01.citrite.net> (raw) Message-ID: <20190410155524.OffllgTFqu9jaKf70WOhGpcArlTVw_tU5XBzrYvlMsA@z> (raw) In-Reply-To: <20190410155217.GH1435@perard.uk.xensource.com> > -----Original Message----- > From: Anthony PERARD [mailto:anthony.perard@citrix.com] > Sent: 10 April 2019 16:52 > To: Paul Durrant <Paul.Durrant@citrix.com> > Cc: qemu-devel@nongnu.org; xen-devel@lists.xenproject.org; qemu-block@nongnu.org; Stefano Stabellini > <sstabellini@kernel.org>; Stefan Hajnoczi <stefanha@redhat.com>; Kevin Wolf <kwolf@redhat.com>; Max > Reitz <mreitz@redhat.com> > Subject: Re: [PATCH] xen-block: support feature-large-sector-size > > On Tue, Apr 09, 2019 at 05:40:38PM +0100, Paul Durrant wrote: > > A recent Xen commit [1] clarified the semantics of sector based quantities > > used in the blkif protocol such that it is now safe to create a xen-block > > device with a logical_block_size != 512, as long as the device only > > connects to a frontend advertizing 'feature-large-block-size'. > > > > This patch modifies xen-block accordingly. It also uses a stack variable > > for the BlockBackend in xen_block_realize() to avoid repeated dereferencing > > of the BlockConf pointer, and changes the parameters of > > xen_block_dataplane_create() so that the BlockBackend pointer and sector > > size are passed expicitly rather than implicitly via the BlockConf. > > > > These modifications have been tested against a recent Windows PV XENVBD > > driver [2] using a xen-disk device with a 4kB logical block size. > > > > [1] http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=67e1c050e36b2c9900cca83618e56189effbad98 > > [2] https://winpvdrvbuild.xenproject.org:8080/job/XENVBD-master/126 > > > > Signed-off-by: Paul Durrant <paul.durrant@citrix.com> > > --- > > diff --git a/hw/block/xen-block.c b/hw/block/xen-block.c > > index ef635be4c2..05e890ad78 100644 > > --- a/hw/block/xen-block.c > > +++ b/hw/block/xen-block.c > > @@ -51,11 +51,25 @@ static void xen_block_connect(XenDevice *xendev, Error **errp) > [...] > > + if (xen_device_frontend_scanf(xendev, "feature-large-sector-size", "%u", > > + &feature_large_sector_size) != 1) { > > + feature_large_sector_size = 0; > > + } > > + > > + if (feature_large_sector_size != 1 && > > + conf->logical_block_size != XEN_BLKIF_SECTOR_SIZE) { > > + error_setg(errp, "logical_block_size != %u not supported", > > Maybe add "by frontend" to the error message? Yes, I'm fine with that addition. > > > + XEN_BLKIF_SECTOR_SIZE); > > + return; > > + } > > + > > With the question answered: > Reviewed-by: Anthony PERARD <anthony.perard@citrix.com> > Thanks, Paul > Thanks, > > -- > Anthony PERARD
next prev parent reply other threads:[~2019-04-10 15:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-09 16:40 [Qemu-devel] [PATCH] xen-block: support feature-large-sector-size Paul Durrant 2019-04-09 16:40 ` Paul Durrant 2019-04-10 15:52 ` Anthony PERARD 2019-04-10 15:52 ` Anthony PERARD 2019-04-10 15:55 ` Paul Durrant [this message] 2019-04-10 15:55 ` Paul Durrant 2019-06-26 16:48 ` Max Reitz 2019-06-26 17:19 ` Anthony PERARD 2019-06-26 17:48 ` Max Reitz
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=f76a3a96fabc4afbb96586a9b5fe682f@AMSPEX02CL01.citrite.net \ --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: linkBe 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; as well as URLs for NNTP newsgroup(s).