From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: remove malloc tracing
Date: Thu, 8 Oct 2015 15:20:49 +0100 [thread overview]
Message-ID: <20151008142049.GJ14090@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1442417924-25831-1-git-send-email-pbonzini@redhat.com>
On Wed, Sep 16, 2015 at 05:38:44PM +0200, Paolo Bonzini wrote:
> The malloc vtable is not supported anymore in glib, because it broke
> when constructors called g_malloc. Remove tracing of g_malloc,
> g_realloc and g_free calls.
>
> Note that, for systemtap users, glib also provides tracepoints
> glib.mem_alloc, glib.mem_free, glib.mem_realloc, glib.slice_alloc
> and glib.slice_free.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> trace-events | 3 ---
> vl.c | 27 ---------------------------
> 2 files changed, 30 deletions(-)
Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan
next prev parent reply other threads:[~2015-10-08 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 15:38 [Qemu-devel] [PATCH] trace: remove malloc tracing Paolo Bonzini
2015-10-07 15:21 ` Alberto Garcia
2015-10-08 14:20 ` Stefan Hajnoczi [this message]
2015-10-08 14:31 ` Peter Maydell
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=20151008142049.GJ14090@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).