* [Qemu-devel] [PATCH] tracing: start trace processing thread in final child process
@ 2013-09-23 14:36 Christian Borntraeger
2013-09-24 12:43 ` Stefan Hajnoczi
0 siblings, 1 reply; 2+ messages in thread
From: Christian Borntraeger @ 2013-09-23 14:36 UTC (permalink / raw)
To: Stefan Hajnoczi
Cc: Christian Borntraeger, Lluís, Michael Mueller, qemu-devel
From: Michael Mueller <mimu@linux.vnet.ibm.com>
When running with trace backend e.g. "simple" the writer thread needs to be
implemented in the same process context as the trace points that will be
processed. Under libvirtd control, qemu gets first started in daemonized
mode to privide its capabilities. Creating the writer thread in the initial
process context then leads to a dead lock because the thread gets termined
together with the initial parent. (-daemonize)
Signed-off-by: Michael Mueller <mimu@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
[minor whitespace fixes]
---
vl.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 4e709d5..93670c8 100644
--- a/vl.c
+++ b/vl.c
@@ -3863,8 +3863,10 @@ int main(int argc, char **argv, char **envp)
qemu_set_log(mask);
}
- if (!trace_backend_init(trace_events, trace_file)) {
- exit(1);
+ if (!is_daemonized()) {
+ if (!trace_backend_init(trace_events, trace_file)) {
+ exit(1);
+ }
}
/* If no data_dir is specified then try to find it relative to the
@@ -4358,6 +4360,12 @@ int main(int argc, char **argv, char **envp)
os_setup_post();
+ if (is_daemonized()) {
+ if (!trace_backend_init(trace_events, trace_file)) {
+ exit(1);
+ }
+ }
+
main_loop();
bdrv_close_all();
pause_all_vcpus();
--
1.8.3.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] [PATCH] tracing: start trace processing thread in final child process
2013-09-23 14:36 [Qemu-devel] [PATCH] tracing: start trace processing thread in final child process Christian Borntraeger
@ 2013-09-24 12:43 ` Stefan Hajnoczi
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Hajnoczi @ 2013-09-24 12:43 UTC (permalink / raw)
To: Christian Borntraeger; +Cc: qemu-devel, Lluís, Michael Mueller
On Mon, Sep 23, 2013 at 04:36:54PM +0200, Christian Borntraeger wrote:
> From: Michael Mueller <mimu@linux.vnet.ibm.com>
>
> When running with trace backend e.g. "simple" the writer thread needs to be
> implemented in the same process context as the trace points that will be
> processed. Under libvirtd control, qemu gets first started in daemonized
> mode to privide its capabilities. Creating the writer thread in the initial
> process context then leads to a dead lock because the thread gets termined
> together with the initial parent. (-daemonize)
>
> Signed-off-by: Michael Mueller <mimu@linux.vnet.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> [minor whitespace fixes]
> ---
> vl.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-09-24 12:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-23 14:36 [Qemu-devel] [PATCH] tracing: start trace processing thread in final child process Christian Borntraeger
2013-09-24 12:43 ` Stefan Hajnoczi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).