Skip to content

CHANGELOG.md

Latest commit

 

History

History
63 lines (43 loc) · 1.98 KB

CHANGELOG.md

File metadata and controls

63 lines (43 loc) · 1.98 KB
Raw

Upcoming release

Changed

  • [114] Cargo.toml: Update deps to latest version

  • [103] Functions that map memory into the VFIO device are now marked as unsafe. The caller of these functions is responsible for enforcing various complex but documented invariants to avoid undefined behavior. This requirement is also present in previous versions of the crate, but the function was not marked unsafe and the invariants were not documented.

    In the future a high-level safe API will be provided that avoids these requirements at the cost of some flexibility.

Added

Fixed

[v0.5.1]

Changed

  • [111] vfio-ioctls: upgrade mshv-bindings and mshv-ioctls

[v0.5.0]

Changed

  • [86] Upgrade vmm sys utils to v0.14.0
  • [87] vfio-ioctls: Upgrade kvm-ioctl & kvm-bindings crates
  • [88] Bump thiserror to latest version

[v0.4.0]

Added

  • Enable support for Microsoft Hyper-V.
  • VfioError now propagates the underlying error for more error types.
  • Many structs now derive Eq where it makes sense.
  • Added VfioDevice::set_irq_resample_fd to unmask level-triggered IRQs via an eventfd.

Changed

  • We skipped to version 0.4.0 to harmonize versions with vfio-bindings.
  • The device handle in VfioContainer::new has become optional.
  • Device file descriptors have their own type (VfioDeviceFd) to hide the underlying hypervisor-specific types.
  • Fixed file descriptor handling on big endian architectures.
  • Avoid logging errors for querying VGA regions for devices that don't have them.

[v0.1.0]

This is the first vfio-ioctl crate release.

This crate provides higher-level abstractions for the Virtual Function I/O (VFIO) Linux kernel API.