[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220826184500.1940077-2-vipinsh@google.com>
Date: Fri, 26 Aug 2022 11:44:57 -0700
From: Vipin Sharma <vipinsh@...gle.com>
To: seanjc@...gle.com, dmatlack@...gle.com, pbonzini@...hat.com
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Vipin Sharma <vipinsh@...gle.com>
Subject: [PATCH v3 1/4] KVM: selftests: Explicitly set variables based on
options in dirty_log_perf_test
Variable set via -g are also indirectly set by -e option by omitting
break statement. Set them explicitly so that movement of switch-case
statements does not unintentionally break features.
No functional change intended.
Signed-off-by: Vipin Sharma <vipinsh@...gle.com>
---
tools/testing/selftests/kvm/dirty_log_perf_test.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/kvm/dirty_log_perf_test.c b/tools/testing/selftests/kvm/dirty_log_perf_test.c
index f99e39a672d3..a03db7f9f4c0 100644
--- a/tools/testing/selftests/kvm/dirty_log_perf_test.c
+++ b/tools/testing/selftests/kvm/dirty_log_perf_test.c
@@ -411,6 +411,8 @@ int main(int argc, char *argv[])
case 'e':
/* 'e' is for evil. */
run_vcpus_while_disabling_dirty_logging = true;
+ dirty_log_manual_caps = 0;
+ break;
case 'g':
dirty_log_manual_caps = 0;
break;
--
2.37.2.672.g94769d06f0-goog
Powered by blists - more mailing lists