commit 5bb795076ba20ba525e443f35dc3e4fb4f84ba95
author Alice Wang <aliceywang@google.com> Mon Jun 12 09:25:07 2023 +0000
committer Alice Wang <aliceywang@google.com> Mon Jun 12 09:25:07 2023 +0000
tree a7ce792270672af24c7cc8a7eca8328bd8f7c9ca
parent e72729e18a2d166bf116f6784897fcdc86a19f33

[vmbase] Change payload_range in MemoryTracker to Option

As this parameter is needed in pvmfw but not in rialto.

Bug: 284462758
Test: m pvmfw_img
Change-Id: Iaed98a7f4a7d4e98b2fc59e9de8e277608a9a5e2

pvmfw/src/entry.rs

diff --git a/pvmfw/src/entry.rs b/pvmfw/src/entry.rs
index a4b8a64..fc96e53 100644
--- a/pvmfw/src/entry.rs
+++ b/pvmfw/src/entry.rs
@@ -229,7 +229,7 @@
         page_table,
         crosvm::MEM_START..memory::MAX_ADDR,
         crosvm::MMIO_START..crosvm::MMIO_END,
-        memory::appended_payload_range(),
+        Some(memory::appended_payload_range()),
     ));
 
     let slices = MemorySlices::new(fdt, payload, payload_size)?;