virtio-queue-ser-v0.9.0

Changed

• Updated virtio-queue from 0.11.0 to 0.12.0.

virtio-queue-ser-v0.8.0

Changed

• Updated vm-memory from 0.13.1 to 0.14.0.
• Updated virtio-queue from 0.10.0 to 0.11.0.
• Updated versionize from 0.1.6 to 0.2.0.

virtio-queue-v0.10.0

Identical to v0.9.1, which was incorrectly published as minor release.

Changed

• Updated vm-memory from 0.12.0 to 0.13.1.
• Updated dev-dependencies:
  • criterion (0.3.0 -> 0.5.1)
  • memoffset (0.7.1 -> 0.9.0)

virtio-queue-ser-v0.7.0

Changes

• Updated virtio-queue from 0.9.1 to 0.10.0.

virtio-bindings-v0.2.2

Added

• Added bindings for virtio_ids.h
• Regenerate bindings with Linux 6.4.

virtio-vsock-v0.3.0

Changes

• Updated vm-memory from 0.10.0 to 0.11.0.
• Updated virtio-queue from 0.7.0 to 0.8.0.

virtio-queue v0.8.0

Changed

• Terminate iterating descriptor chains that are longer than 2^32 bytes.
• Updated vm-memory from 0.10.0 to 0.11.0.
• Updated virtio-bindings from 0.1.0 to 0.2.0.

virtio-queue-ser v0.5.0

Changed

• Updated vm-memory from 0.10.0 to 0.11.0.
• Updated virtio-queue from 0.7.1 to 0.8.0.

virtio-bindings v0.2.0

Added

• Add bindings for virtio_config.h, virtio_gpu.h, and virtio_mmio.h

Changed

• Regenerate bindings with Glibc 2.36, Linux 6.1, and bindgen 0.63.0
• The virtio-v4_14_0 and virtio-v5_0_0 crate features are now no-ops — the latest version of the bindings is now always used.
• The bindings modules no longer accidentally re-export constants from Glibc or other kernel headers. As a result of this, it is no longer possible to reference constants from virtio_config.h through e.g. the virtio_net module, only through the virtio_config module.

virtio-queue v0.7.1

Fixed

• Skip indirect descriptor address alignment check, the virtio spec has no alignment requirement on this, see 2.6.5.3 Indirect Descriptors and 2.7.7 Indirect Flag: Scatter-Gather Support in virtio 1.0.
• Update the add_desc_chains mock function such that it works on big endian hosts as well.
• Check that the queue is ready for processing requests when calling the iterator functions. For now the checks are limited to the avail address and the ready fields, but should be extended in the future to account for other fields that could signal an invalid queue. This behavior can be triggered by doing a reset followed by a pop_descriptor_chain.