search for: define_prop64_bit

...That's quite tricky to use correctly. > Why don't we just make it uint64_t? ...and another one was that at least virtio-ccw reads/writes in chunks of 32 bits anyway. > > The only real issue is that DEFINE_PROP_BIT wants > a uint32_t. > > But that's easy to fix: add DEFINE_PROP64_BIT > that is the same but handles a 64 bit array. > Sure, this would not really be a problem to add. But we'll stand before the same problem again when we want to grow past 64 bits, won't we?

...That's quite tricky to use correctly. > Why don't we just make it uint64_t? ...and another one was that at least virtio-ccw reads/writes in chunks of 32 bits anyway. > > The only real issue is that DEFINE_PROP_BIT wants > a uint32_t. > > But that's easy to fix: add DEFINE_PROP64_BIT > that is the same but handles a 64 bit array. > Sure, this would not really be a problem to add. But we'll stand before the same problem again when we want to grow past 64 bits, won't we?

...s[NR_VIRTIO_FEATURE_WORDS]; > size_t config_len; > void *config; > uint16_t config_vector; Ugh. That's quite tricky to use correctly. Why don't we just make it uint64_t? The only real issue is that DEFINE_PROP_BIT wants a uint32_t. But that's easy to fix: add DEFINE_PROP64_BIT that is the same but handles a 64 bit array. -- MST

With virtio-1, we support more than 32 feature bits. Let's make vdev->guest_features depend on the number of supported feature bits, allowing us to grow the feature bits automatically. We also need to enhance the internal functions dealing with getting and setting features with an additional index field, so that all feature bits may be accessed (in chunks of 32 bits). vhost and migration

With virtio-1, we support more than 32 feature bits. Let's make vdev->guest_features depend on the number of supported feature bits, allowing us to grow the feature bits automatically. We also need to enhance the internal functions dealing with getting and setting features with an additional index field, so that all feature bits may be accessed (in chunks of 32 bits). vhost and migration

Yet another version of the virtio-1 support patches. This one has seen some (very) light testing with the virtio-1 guest support patches currently on vhost-next. Changes from v3: - Add support for FEATURES_OK. We refuse to set features after the driver has set this in the status field, and we allow to fail setting the status if the features are inconsistent. - Add missing virtio-1 changes

Yet another version of the virtio-1 support patches. This one has seen some (very) light testing with the virtio-1 guest support patches currently on vhost-next. Changes from v3: - Add support for FEATURES_OK. We refuse to set features after the driver has set this in the status field, and we allow to fail setting the status if the features are inconsistent. - Add missing virtio-1 changes