summary refs log tree commit diff stats
path: root/scripts/tracetool/backend/ust.py
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2014-02-17 14:54:17 +0100
committerStefan Hajnoczi <stefanha@redhat.com>2014-02-19 15:44:34 +0100
commitcef60c925c41563721dc73b1ace7b2f399f72a5b (patch)
tree270b17012bd476ee5245a83c2dceaa6e806a6e1c /scripts/tracetool/backend/ust.py
parent98f9e35befe5c11e3da448cbe015969ed91730a4 (diff)
downloadfocaccia-qemu-cef60c925c41563721dc73b1ace7b2f399f72a5b.tar.gz
focaccia-qemu-cef60c925c41563721dc73b1ace7b2f399f72a5b.zip
qtest: make QEMU our direct child process
qtest_init() cannot use exec*p() to launch QEMU since the exec*p()
functions take an argument array while qtest_init() takes char
*extra_args.  Therefore we execute /bin/sh -c <command-line> and let the
shell parse the argument string.

This left /bin/sh as our child process and our child's child was QEMU.
We still want QEMU's pid so the -pidfile option was used to let QEMU
report its pid.

The pidfile needs to be unlinked when the test case exits or fails.  In
other words, the pidfile creates a new problem for us!

Simplify all this using the shell 'exec' command.  It allows us to
replace the /bin/sh process with QEMU.  Then we no longer need to use
-pidfile because we already know our fork child's pid.

Note: Yes, it seems silly to exec /bin/sh when we could just exec QEMU
directly.  But remember qtest_init() takes a single char *extra_args
command-line fragment instead of a real argv[] array, so we need
/bin/sh's argument parsing behavior.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'scripts/tracetool/backend/ust.py')
0 files changed, 0 insertions, 0 deletions