On Tue, Sep 10, 2024 at 04:01:50PM +0200, Jürgen Groß wrote:
> On 10.09.24 15:59, Roger Pau Monné wrote:
> > On Tue, Sep 10, 2024 at 03:46:00PM +0200, Jürgen Groß wrote:
> > > On 10.09.24 13:46, Roger Pau Monne wrote:
> > > > diff --git a/xen/include/public/io/blkif.h
> > > > b/xen/include/public/
On 10.09.24 15:59, Roger Pau Monné wrote:
On Tue, Sep 10, 2024 at 03:46:00PM +0200, Jürgen Groß wrote:
On 10.09.24 13:46, Roger Pau Monne wrote:
Current blkif implementations (both backends and frontends) have all slight
differences about how they handle the 'sector-size' xenstore node, and how
On Tue, Sep 10, 2024 at 03:46:00PM +0200, Jürgen Groß wrote:
> On 10.09.24 13:46, Roger Pau Monne wrote:
> > Current blkif implementations (both backends and frontends) have all slight
> > differences about how they handle the 'sector-size' xenstore node, and how
> > other fields are derived from t
On 10.09.24 13:46, Roger Pau Monne wrote:
Current blkif implementations (both backends and frontends) have all slight
differences about how they handle the 'sector-size' xenstore node, and how
other fields are derived from this value or hardcoded to be expressed in units
of 512 bytes.
To give so
Current blkif implementations (both backends and frontends) have all slight
differences about how they handle the 'sector-size' xenstore node, and how
other fields are derived from this value or hardcoded to be expressed in units
of 512 bytes.
To give some context, this is an excerpt of how differ
