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
There is only a single error condition, so we can indicate the error
case with an Option. First step towards untangling the region specific
errors from the region collection specific errors.
Signed-off-by: Patrick Roy <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,9 @@
16
16
a default implementation, based on linear search.
17
17
-\[[#312](https://github.com/rust-vmm/vm-memory/pull/312)\]: Provide a marker trait, `GuestMemoryRegionBytes`, which enables a default implementation of `Bytes<MemoryRegionAddress>`
18
18
for a `GuestMemoryRegion` if implemented.
19
-
19
+
-\[[#312](https://github.com/rust-vmm/vm-memory/pull/312)\]: Adjust error types returned from `GuestMemoryMmap::from_ranges[_with_files]`
20
+
and `GuestRegionMmap::from_range` to be separate from the error type returned by `GuestRegionCollection` functions.
21
+
Change return type of `GuestRegionMmap::new` from `Result` to `Option`.
20
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()`.
0 commit comments