On Wed, Feb 13, 2019 at 6:07 PM Michael S. Tsirkin <m...@redhat.com> wrote:
> On Wed, Feb 13, 2019 at 01:17:03PM +0100, Stefano Garzarella wrote:
> >
> > In my series "[PATCH v4 0/6] virtio-blk: add DISCARD and WRITE_ZEROES"
> > I'm adding the host_features field in VirtIOBlock. Then, I could add
> > something like the following patch (proof of concept) inspired by the
> > virtio-net approach, that would be simplest to maintain when we will add
> > new features.
> >
> > What do you think?
> >
> > Thanks,
> > Stefano
> >
> >
> > diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
> > index 843bb2bec8..84dcc1406c 100644
> > --- a/hw/block/virtio-blk.c
> > +++ b/hw/block/virtio-blk.c
> > @@ -28,6 +28,51 @@
> > #include "hw/virtio/virtio-bus.h"
> > #include "hw/virtio/virtio-access.h"
> >
> > +/*
> > + * Calculate the number of bytes up to and including the given 'field' of
> > + * 'container'.
> > + */
> > +#define endof(container, field) \
> > + (offsetof(container, field) + sizeof_field(container, field))
> > +
>
> e.g. virtio.h. just add virtio prefix.
Make sense, maybe also the VirtIOFeature defined below can go in virtio.h.
>
> > +typedef struct VirtIOFeature {
> > + uint64_t flags;
> > + size_t end;
> > +} VirtIOFeature;
> > +
> > +static VirtIOFeature feature_sizes[] = {
> > + {.flags = 1ULL << VIRTIO_NET_F_SIZE_MAX,
> > + .end = endof(struct virtio_blk_config, size_max)},
> > + {.flags = 1ULL << VIRTIO_NET_F_SEG_MAX,
> > + .end = endof(struct virtio_blk_config, seg_max)},
> > + {.flags = 1ULL << VIRTIO_NET_F_GEOMETRY,
> > + .end = endof(struct virtio_blk_config, geometry)},
> > + {.flags = 1ULL << VIRTIO_NET_F_BLK_SIZE,
> > + .end = endof(struct virtio_blk_config, blk_size)},
> > + {.flags = 1ULL << VIRTIO_NET_F_TOPOLOGY,
> > + .end = endof(struct virtio_blk_config, opt_io_size)},
> > + {.flags = 1ULL << VIRTIO_NET_F_CONFIG_WCE,
> > + .end = endof(struct virtio_blk_config, wce)},
> > + {.flags = 1ULL << VIRTIO_NET_F_MQ,
> > + .end = endof(struct virtio_blk_config, num_queues)},
> > + {}
>
> All names above with net look wrong to me.
Yes, they are wrong :) s/NET/BLK
I'm not sure if using the feature_sizes array the migration works well.
I mean if we have QEMU 3.1 with a single queue and we want to migrate to
QEMU 4.0 with a single queue, the config_size could be different,
because VIRTIO_NET_F_MQ is not set in the host_features.
Maybe we should initialize a config_size to the VIRTIO_BLK_CFG_SIZE macro
defined by Changpeng and then use the feature_sizes arrays only for the
new features (i.e. discard, write_zeroes)
What do you think?
>
> > +};
> > +
> > +static void virtio_blk_set_config_size(VirtIOBlock *s, uint64_t
> > host_features)
> > +{
> > + int i, config_size;
> > +
> > + config_size = endof(struct virtio_blk_config, capacity);
> > +
> > + for (i = 0; feature_sizes[i].flags != 0; i++) {
> > + if (host_features & feature_sizes[i].flags) {
> > + config_size = MAX(feature_sizes[i].end, config_size);
> > + }
> > + }
> > +
> > + s->config_size = config_size;
> > +}
> > +
>
> Put this in virtio.c maybe? size can be returned.
Do you want to reuse it also in virtio-net?
I should add some parameters (feature_sizes pointer and len), but I
think can work.
Thanks,
Stefano
