linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tz.stoyanov@gmail.com
To: rostedt@goodmis.org, y.karadz@gmail.com
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] Save tracee memory map into trace.dat file
Date: Mon, 17 Jun 2019 14:52:16 +0300	[thread overview]
Message-ID: <20190617115218.6279-1-tz.stoyanov@gmail.com> (raw)

From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>

New trace-cmd option is introduced, "--mmap". When it is used together
with -F or -P options, the memory map of the traced applications is
stored into the trace.dat file. The new API tracecmd_search_tracee_mmap()
can be used to do lookups into those memory maps.


Tzvetomir Stoyanov (1):
  trace-cmd: Implemented new API tracecmd_add_option_v()

Tzvetomir Stoyanov (VMware) (1):
  trace-cmd: Save the tracee memory map into the trace.dat file.

 include/trace-cmd/trace-cmd.h    |   9 +++
 include/traceevent/event-parse.h |   1 +
 lib/trace-cmd/trace-input.c      |  81 ++++++++++++++++++++
 tracecmd/include/trace-local.h   |  16 ++++
 tracecmd/trace-output.c          | 117 ++++++++++++++++++++++++-----
 tracecmd/trace-record.c          | 123 +++++++++++++++++++++++++++++++
 6 files changed, 330 insertions(+), 17 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-06-17 11:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 11:52 tz.stoyanov [this message]
2019-06-17 11:52 ` [PATCH 1/2] trace-cmd: Implemented new API tracecmd_add_option_v() tz.stoyanov
2019-06-17 13:06   ` Steven Rostedt
2019-06-17 13:18     ` Ceco
2019-06-17 13:39       ` Steven Rostedt
2019-06-17 11:52 ` [PATCH 2/2] trace-cmd: Save the tracee memory map into the trace.dat file tz.stoyanov
2019-06-17 13:37   ` Steven Rostedt
2019-06-17 14:12     ` Steven Rostedt

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=20190617115218.6279-1-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=y.karadz@gmail.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).