From: Stefan Hajnoczi <stefanha@gmail.com>
To: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v7 0/3] Simpletrace v2: Support multiple args, strings.
Date: Tue, 17 Jul 2012 15:07:05 +0100 [thread overview]
Message-ID: <CAJSP0QXi5LZZ8V+t_iDuqj9FqjiRfBN0nn2QBiQYkoWp3fboDA@mail.gmail.com> (raw)
In-Reply-To: <1341307259-27262-1-git-send-email-harsh@linux.vnet.ibm.com>
On Tue, Jul 3, 2012 at 10:20 AM, Harsh Prateek Bora
<harsh@linux.vnet.ibm.com> wrote:
> Existing simpletrace backend allows to trace at max 6 args and does not
> support strings. This newer tracelog format gets rid of fixed size records
> and therefore allows to trace variable number of args including strings.
>
> Sample trace:
> v9fs_version 0.000 tag=0xffff id=0x64 msize=0x2000 version=9P2000.L
> v9fs_version_return 6.705 tag=0xffff id=0x64 msize=0x2000 version=9P2000.L
> v9fs_attach 174.467 tag=0x1 id=0x68 fid=0x0 afid=0xffffffffffffffff
> uname=nobody aname=
> v9fs_attach_return 4720.454 tag=0x1 id=0x68 type=0xffffffffffffff80
> version=0x4f2a4dd0 path=0x220ea6
The writeout thread deadlocked itself when it called g_malloc() and
therefore became a tracing thread:
Thread 3 (Thread 0x7fad8b144700 (LWP 1387)):
#0 0x00007ffffa1e88de in ?? ()
#1 0x00007fad9421de86 in *__GI_clock_gettime
(clock_id=clock_id@entry=1, tp=tp@entry=0x7fad8b143be0) at
../sysdeps/unix/clock_gettime.c:116
#2 0x00007fad94813e46 in get_clock () at ./qemu-timer.h:124
#3 trace_record_start (rec=rec@entry=0x7fad8b143c10,
event=140383339428832, event@entry=0, datasize=datasize@entry=16) at
trace/simple.c:219
#4 0x00007fad947f7185 in trace_g_malloc (size=size@entry=32,
ptr=ptr@entry=0x7fad340008b0) at trace.c:770
#5 0x00007fad947b5754 in malloc_and_trace (n_bytes=32) at
/home/stefanha/qemu/vl.c:2240
#6 0x00007fad93d70de1 in g_malloc (n_bytes=n_bytes@entry=32) at
/tmp/buildd/glib2.0-2.32.3/./glib/gmem.c:159
#7 0x00007fad94813bce in get_trace_record (recordptr=<synthetic
pointer>, idx=56943) at trace/simple.c:114
#8 writeout_thread (opaque=<optimized out>) at trace/simple.c:189
#9 0x00007fad93d8ddf5 in g_thread_proxy (data=0x7fad96738800) at
/tmp/buildd/glib2.0-2.32.3/./glib/gthread.c:801
#10 0x00007fad90ed7b50 in start_thread (arg=<optimized out>) at
pthread_create.c:304
#11 0x00007fad90c226dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()
Stefan
next prev parent reply other threads:[~2012-07-17 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 9:20 [Qemu-devel] [PATCH v7 0/3] Simpletrace v2: Support multiple args, strings Harsh Prateek Bora
2012-07-03 9:20 ` [Qemu-devel] [PATCH v7 1/3] monitor: remove unused do_info_trace Harsh Prateek Bora
2012-07-03 9:20 ` [Qemu-devel] [PATCH v7 2/3] Simpletrace v2: Support multiple arguments, strings Harsh Prateek Bora
2012-07-17 15:21 ` Stefan Hajnoczi
2012-07-17 19:01 ` Harsh Bora
2012-07-17 20:08 ` Harsh Bora
2012-07-18 8:59 ` Stefan Hajnoczi
2012-07-18 8:53 ` Stefan Hajnoczi
2012-07-03 9:20 ` [Qemu-devel] [PATCH v7 3/3] Update simpletrace.py for new log format Harsh Prateek Bora
2012-07-17 14:07 ` Stefan Hajnoczi [this message]
2012-07-17 14:14 ` [Qemu-devel] [PATCH v7 0/3] Simpletrace v2: Support multiple args, strings Stefan Hajnoczi
2012-07-17 15:23 ` Stefan Hajnoczi
2012-07-17 19:51 ` Harsh Bora
2012-07-18 8:51 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJSP0QXi5LZZ8V+t_iDuqj9FqjiRfBN0nn2QBiQYkoWp3fboDA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=harsh@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).