On 5/2/23 05:29, Alexander Bulekov wrote:
As we are converting most fuzzers to rely on reboots to reset state,
introduce an API to make sure reboots are invoked in a consistent
manner.
Signed-off-by: Alexander Bulekov <alx...@bu.edu>
---
tests/qtest/fuzz/fuzz.c | 6 ++++++
tests/qtest/fuzz/fuzz.h | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/tests/qtest/fuzz/fuzz.c b/tests/qtest/fuzz/fuzz.c
index eb7520544b..c2d07a4c7e 100644
--- a/tests/qtest/fuzz/fuzz.c
+++ b/tests/qtest/fuzz/fuzz.c
@@ -51,6 +51,12 @@ void flush_events(QTestState *s)
}
}
+void fuzz_reboot(QTestState *s)
"reboot" sounds like guest software triggered.
IIUC from the fuzzer PoV this is more a "power-cycle" right?
+{
+ qemu_system_reset(SHUTDOWN_CAUSE_GUEST_RESET);
Is SHUTDOWN_CAUSE_HOST_QMP_SYSTEM_RESET more appropriate?
+ main_loop_wait(true);
+}
