build(deps): bump the rust-dependencies group across 1 directory with 2 updates

[dependabot]

Updates the requirements on vm-memory and criterion to permit the latest version.
Updates vm-memory to 0.18.0

Changelog

Sourced from vm-memory's changelog.

0.18.0

Changed

This release includes a major change to the vm-memory API in order to support memory access permissions. The previous GuestMemory trait is now renamed to GuestMemoryBackend, and GuestMemory has a completely new definition. However, common interfaces such as GuestAddressSpace and Bytes remain on GuestMemory; therefore, all callers that just use the Bytes interface remain completely unchanged.

• [#362] Rename GuestMemory to GuestMemoryBackend, IoMemory to GuestMemory

Added

• [#327] I/O virtual memory support via IoMemory, IommuMemory, and Iommu/Iotlb

Fixed

• [#361] clippy: allow mut_from_ref

[v0.17.1]

No visible changes.

[v0.17.0]

Added

• [#311] Allow compiling without the ReadVolatile and WriteVolatile implementations
• [#312] GuestRegionContainer, a generic container of GuestMemoryRegions, generalizing GuestMemoryMmap (which is now a type alias for GuestRegionContainer<GuestRegionMmap>).
• [#338] Make GuestMemoryAtomic always implement Clone.
• [#338] Make GuestAddressSpace a subtrait of Clone.
• [#339] Add GuestMemory::get_slices()

Changed

• [#307] Move read_volatile_from, read_exact_volatile_from, write_volatile_to and write_all_volatile_to functions from the GuestMemory trait to the Bytes trait.
• [#312]: Give GuestMemory::find_region and GuestMemory::num_regions a default implementation, based on linear search.
• [#312]: Provide a marker trait, GuestMemoryRegionBytes, which enables a default implementation of Bytes<MemoryRegionAddress> for a GuestMemoryRegion if implemented.
• [#312]: Adjust error types returned from GuestMemoryMmap::from_ranges[_with_files] and GuestRegionMmap::from_range to be separate from the error type returned by GuestRegionCollection functions. Change return type of GuestRegionMmap::new from Result to Option.
• [#324](rust-vmm/vm-memory#324 GuestMemoryRegion::bitmap() now returns a BitmapSlice. Accessing the full bitmap is now possible only if the type of the memory region is know, for example with MmapRegion::bitmap().
• [#339] Implement Bytes::load() and Bytes::store() with get_slices() instead of to_region_addr()

... (truncated)

Commits

• b6404d2 Bump version to 0.18.0
• 3e868f1 Emphasize GuestMemory more in the documentation
• da8fc34 Reformat after the rename
• f5c882e The small rename - iterators
• 7e7cad2 The great rename
• fed3a63 chore: update coverage
• 91220ed chore: fix clippy lints/cargo warnings
• 3cdd259 build(deps): bump rust-vmm-ci from 042b206 to b4bb768
• 8c4c815 Have SimpleIommu depend on backend-mmap
• 4ce4235 clippy: allow mut_from_ref
• Additional commits viewable in compare view

Updates criterion to 0.8.1

Release notes

Sourced from criterion's releases.

criterion-plot-v0.8.1

Fixed

• Typo

Changelog

Sourced from criterion's changelog.

0.8.1 - 2025-12-07

Fixed

• Homepage link

Other

• (deps) bump crate-ci/typos from 1.23.5 to 1.40.0
• (deps) bump jontze/action-mdbook from 3 to 4
• (deps) bump actions/checkout from 4 to 6

0.8.0 - 2025-11-29

BREAKING

• Drop async-std support

Changed

• Bump MSRV to 1.86, stable to 1.91.1

Added

• Add ability to plot throughput on summary page.
• Add support for reporting throughput in elements and bytes - Throughput::ElementsAndBytes allows the text summary to report throughput in both units simultaneously.
• Add alloca-based memory layout randomisation to mitigate memory effects on measurements.
• Add doc comment to benchmark runner in criterion_group macro (removes linter warnings)

Fixed

• Fix plotting NaN bug

Other

• Remove Master API Docs links temporarily while we restore the docs publishing.

[0.7.0] - 2025-07-25

• Bump version of criterion-plot to align dependencies.

[0.6.0] - 2025-05-17

Changed

• MSRV bumped to 1.80
• The real_blackbox feature no longer has any impact. Criterion always uses std::hint::black_box() now. Users of criterion::black_box() should switch to std::hint::black_box().
• clap dependency unpinned.

Fixed

... (truncated)

Commits

• e4e06df chore: release v0.8.1
• aa548b9 fix: Homepage link
• 950c3b7 fix: Typo
• 7e3e50c chore(deps): bump crate-ci/typos from 1.23.5 to 1.40.0
• 391a99a chore(deps): bump jontze/action-mdbook from 3 to 4
• 8fb9a87 chore(deps): bump actions/checkout from 4 to 6
• b49ade7 chore: release v0.8.0
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions