When loading a kernel image, kvmtool is nice enough to print a message
informing the user where the file was loaded in guest memory, which is very
useful for debugging. Do the same for the firmware image.
Commit e1c7c62afc7b ("arm: turn pr_info() into pr_debug() messages")
changed various pr_info() into pr_debug() messages to stop kvmtool from
cluttering stdout. Do the same when printing where the FDT has been copied
when loading a firmware image.
Signed-off-by: Alexandru Elisei <alexandru.elisei@xxxxxxx>
---
arm/kvm.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arm/kvm.c b/arm/kvm.c
index 5aea18fedc3e..80d233f13d0b 100644
--- a/arm/kvm.c
+++ b/arm/kvm.c
@@ -218,6 +218,8 @@ bool kvm__load_firmware(struct kvm *kvm, const char *firmware_filename)
/* Kernel isn't loaded by kvm, point start address to firmware */
kvm->arch.kern_guest_start = fw_addr;
+ pr_debug("Loaded firmware to 0x%llx (%zd bytes)",
+ kvm->arch.kern_guest_start, fw_sz);
/* Load dtb just after the firmware image*/
host_pos += fw_sz;
@@ -226,9 +228,9 @@ bool kvm__load_firmware(struct kvm *kvm, const char *firmware_filename)
kvm->arch.dtb_guest_start = ALIGN(host_to_guest_flat(kvm, host_pos),
FDT_ALIGN);
- pr_info("Placing fdt at 0x%llx - 0x%llx",
- kvm->arch.dtb_guest_start,
- kvm->arch.dtb_guest_start + FDT_MAX_SIZE);
+ pr_debug("Placing fdt at 0x%llx - 0x%llx",
+ kvm->arch.dtb_guest_start,
+ kvm->arch.dtb_guest_start + FDT_MAX_SIZE);
return true;
}
--
2.31.1
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
