diff mbox series

[RFC,14/19] fuzz: hard-code a main-loop timeout

Message ID 20190725032321.12721-15-alxndr@bu.edu (mailing list archive)
State New, archived
Headers show
Series Add virtual device fuzzing support | expand

Commit Message

Alexander Bulekov July 25, 2019, 3:23 a.m. UTC 
Signed-off-by: Alexander Oleinik <alxndr@bu.edu>
---
 util/main-loop.c | 3 +++
 1 file changed, 3 insertions(+)

Comments

Paolo Bonzini July 25, 2019, 9:40 a.m. UTC | #1 
On 25/07/19 05:23, Oleinik, Alexander wrote:
>      timeout_ns = qemu_soonest_timeout(timeout_ns,
>                                        timerlistgroup_deadline_ns(
>                                            &main_loop_tlg));
> +#ifdef CONFIG_FUZZ
> +    timeout_ns = 50000;
> +#endif
>  

What is the purpose of this, and should it be instead a MIN(50000,
timeout_ns)?

Paolo
diff mbox series

Patch

diff --git a/util/main-loop.c b/util/main-loop.c
index e3eaa55866..708e6be5eb 100644
--- a/util/main-loop.c
+++ b/util/main-loop.c
@@ -513,6 +513,9 @@  void main_loop_wait(int nonblocking)
     timeout_ns = qemu_soonest_timeout(timeout_ns,
                                       timerlistgroup_deadline_ns(
                                           &main_loop_tlg));
+#ifdef CONFIG_FUZZ
+    timeout_ns = 50000;
+#endif
 
     ret = os_host_main_loop_wait(timeout_ns);
     mlpoll.state = ret < 0 ? MAIN_LOOP_POLL_ERR : MAIN_LOOP_POLL_OK;