refactor: avoid an unwrap in set_kvm_memory_regions

There's no need to use the GuestMemoryMmap to resolve the pointer to the
start of the GuestMemoryRegion by resolving the guest physical address
it starts at - because we literally store that pointer inside the
GuestMemoryRegion, so can just use that.

Signed-off-by: Patrick Roy <[email protected]>

Author: roypat

src/vmm/src/vstate/vm/mod.rs

@@ -95,8 +95,7 @@ impl Vm {
                     slot,
                     guest_phys_addr: region.start_addr().raw_value(),
                     memory_size: region.len(),
-                    // It's safe to unwrap because the guest address is valid.
-                    userspace_addr: guest_mem.get_host_address(region.start_addr()).unwrap() as u64,
+                    userspace_addr: region.as_ptr() as u64,
                     flags,
                 };