[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Block protocol incompatibilities with 4K logical sector size disks

To: Roger Pau Monné <roger.pau@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>
From: Paul Durrant <xadimgnik@xxxxxxxxx>
Date: Mon, 2 Sep 2024 15:19:56 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Owen Smith <owen.smith@xxxxxxxxx>, Mark Syms <mark.syms@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>
Delivery-date: Mon, 02 Sep 2024 14:20:07 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 02/09/2024 09:55, Roger Pau Monné wrote:
[snip]


Thanks for your input.  I would also like to hear from the blktap and
Windows PV drivers maintainers, as the change that I'm proposing here
will require changes to their implementations.

So IIUC you are proposing to refuse to connect to a frontend that setsfeature-large-sector-size if sector-size != 512? Is that right?


  Paul

Follow-Ups:
- Re: Block protocol incompatibilities with 4K logical sector size disks
  - From: Roger Pau Monné

References:
- Re: Block protocol incompatibilities with 4K logical sector size disks
  - From: Roger Pau Monné

Prev by Date: Re: [PATCH] x86/PV: simplify (and thus correct) guest accessor functions
Next by Date: Re: [PATCH v1 2/4] xen/arm: mpu: Define Xen start address for MPU systems
Previous by thread: Re: Block protocol incompatibilities with 4K logical sector size disks
Next by thread: Re: Block protocol incompatibilities with 4K logical sector size disks
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.