Commit 89dc5294 authored by Ben Gardon's avatar Ben Gardon Committed by Paolo Bonzini
Browse files

KVM: selftests: Avoid flooding debug log while populating memory



Peter Xu pointed out that a log message printed while waiting for the
memory population phase of the dirty_log_perf_test will flood the debug
logs as there is no delay after printing the message. Since the message
does not provide much value anyway, remove it.

Reviewed-by: default avatarJacob Xu <jacobhxu@google.com>

Signed-off-by: default avatarBen Gardon <bgardon@google.com>
Message-Id: <20210112214253.463999-3-bgardon@google.com>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
parent f9224a52
Loading
Loading
Loading
Loading
+4 −5
Original line number Diff line number Diff line
@@ -146,8 +146,7 @@ static void run_test(enum vm_guest_mode mode, void *arg)
	/* Allow the vCPU to populate memory */
	pr_debug("Starting iteration %lu - Populating\n", iteration);
	while (READ_ONCE(vcpu_last_completed_iteration[vcpu_id]) != iteration)
		pr_debug("Waiting for vcpu_last_completed_iteration == %lu\n",
			iteration);
		;

	ts_diff = timespec_elapsed(start);
	pr_info("Populate memory time: %ld.%.9lds\n",
@@ -171,9 +170,9 @@ static void run_test(enum vm_guest_mode mode, void *arg)

		pr_debug("Starting iteration %lu\n", iteration);
		for (vcpu_id = 0; vcpu_id < nr_vcpus; vcpu_id++) {
			while (READ_ONCE(vcpu_last_completed_iteration[vcpu_id]) != iteration)
				pr_debug("Waiting for vCPU %d vcpu_last_completed_iteration == %lu\n",
					 vcpu_id, iteration);
			while (READ_ONCE(vcpu_last_completed_iteration[vcpu_id])
			       != iteration)
				;
		}

		ts_diff = timespec_elapsed(start);