You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make mmap_unix.rs and mmap_xen.rs not mutually exclusive
Now that all tension between these two modules is resolves (e.g. no more
code depends on exactly one of these being defined, and tests can
support iterating over multiple supported backends), drop all the
`cfg(not(feature = "xen"))` from across the code base.
Signed-off-by: Patrick Roy <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,9 @@
20
20
and `GuestRegionMmap::from_range` to be separate from the error type returned by `GuestRegionCollection` functions.
21
21
Change return type of `GuestRegionMmap::new` from `Result` to `Option`.
22
22
-\[#324](https:////github.com/rust-vmm/vm-memory/pull/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()`.
23
+
-\[[#317](https://github.com/rust-vmm/vm-memory/pull/317)\]: Make `xen` feature additive, meaning enabling it
24
+
no longer disables the `mmap_unix` module at compile time. For this, various Xen-related structs had to be
0 commit comments