diff options
| author | Alexandru Elisei <alexandru.elisei@arm.com> | 2022-02-14 16:58:29 +0000 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2022-02-16 15:59:20 +0000 |
| commit | c334a68e202eb4f2b912c6c9062c80877bead292 (patch) | |
| tree | 93cda2a340173bbe3379e99c1a15d3aadf007e42 | |
| parent | 9b681b0827d7bae692a29e10d5cc8a8b6ec85e35 (diff) | |
| download | kvmtool-c334a68e202eb4f2b912c6c9062c80877bead292.tar.gz | |
arm: Use pr_debug() to print memory layout when loading a firmware image
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@arm.com>
Link: https://lore.kernel.org/r/20220214165830.69207-3-alexandru.elisei@arm.com
Signed-off-by: Will Deacon <will@kernel.org>
| -rw-r--r-- | arm/kvm.c | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -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; } |