mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-24 04:09:48 +00:00
d39e3bbc39
We don't actually need the guest frame number in the VmMemoryRegionId (it is just an opaque value that needs to be unique for each region), and the frame number calculation depends on the page size, so it's simpler to just use the guest physical address itself without shifting it. Change-Id: I75d181c7e07f79b5e0ba0bf0a1174d4f71263bb8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6027193 Reviewed-by: Elie Kheirallah <khei@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||