You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Rusty Russell c45a6816c1 virtio: explicit advertisement of driver features ... A recent proposed feature addition to the virtio block driver revealed some flaws in the API: in particular, we assume that feature negotiation is complete once a driver's probe function returns. There is nothing in the API to require this, however, and even I didn't notice when it was violated. So instead, we require the driver to specify what features it supports in a table, we can then move the feature negotiation into the virtio core. The intersection of device and driver features are presented in a new 'features' bitmap in the struct virtio_device. Note that this highlights the difference between Linux unsigned-long bitmaps where each unsigned long is in native endian, and a straight-forward little-endian array of bytes. Drivers can still remove feature bits in their probe routine if they really have to. API changes: - dev->config->feature() no longer gets and acks a feature. - drivers should advertise their features in the 'feature_table' field - use virtio_has_feature() for extra sanity when checking feature bits Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		17 years ago
..
Kconfig	virtio: balloon driver	17 years ago
Makefile	virtio: balloon driver	17 years ago
config.c	…
virtio.c	virtio: explicit advertisement of driver features	17 years ago
virtio_balloon.c	virtio: explicit advertisement of driver features	17 years ago
virtio_pci.c	virtio: explicit advertisement of driver features	17 years ago
virtio_ring.c	virtio: ignore corrupted virtqueues rather than spinning.	17 years ago