vmm: reduce verbosity of dirty logging output

Lower several informational messages in the dirty logging path to
debug level.

These messages are noisy in practice and provide little value since
dirty logging is known to work reliably. More useful migration metrics
(e.g., dirty size per iteration) is logged per iteration in subsequent
commits.

Signed-off-by: Philipp Schuster <philipp.schuster@cyberus-technology.de>
On-behalf-of: SAP philipp.schuster@sap.com
This commit is contained in:
Philipp Schuster
2026-03-06 13:28:59 +01:00
committed by Rob Bradford
parent b90634a887
commit d4b5502472

View File

@@ -2673,11 +2673,11 @@ impl Migratable for MemoryManager {
let sub_table = MemoryRangeTable::from_dirty_bitmap(dirty_bitmap, r.gpa, 4096);
if sub_table.regions().is_empty() {
info!("Dirty Memory Range Table is empty");
debug!("Dirty Memory Range Table is empty");
} else {
info!("Dirty Memory Range Table:");
debug!("Dirty Memory Range Table:");
for range in sub_table.regions() {
info!("GPA: {:x} size: {} (KiB)", range.gpa, range.length / 1024);
debug!("GPA: {:x} size: {} (KiB)", range.gpa, range.length / 1024);
}
}