mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-28 17:44:10 +00:00
fb641f67e4
The AddressRange type is used for representing contiguous memory or I/O address ranges, mostly equivalent to RangeInclusive<u64> but with the added benefit of implementing Copy and not carrying an extra field used only for iteration, which we don't need. Using an inclusive range means we can represent the full address space with no weird corner cases around the upper limit of the range (for example, an AddressRange covering the full 64-bit space can be represented as start: 0, end: u64::MAX). AddressRange also replaces the previous MemRegion type, which was a start/size pair. This normalizes the interface of the resources crates to use AddressRange rather than a start/size pair; more cleanups throughout the tree may be possible, but this commit attempts to be somewhat smaller to have a hope of being reviewable. BUG=b:222769529 TEST=tools/presubmit --all TEST=cargo test -p resources Change-Id: I8c90bdc28456221b5107ef7e589233315ea739c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3696671 Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Reviewed-by: David Stevens <stevensd@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||