linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/9 v2] trace-cmd: Fixes for trace-cmd restore
Date: Fri, 05 Mar 2021 17:52:23 -0500	[thread overview]
Message-ID: <20210305225223.794554327@goodmis.org> (raw)

The trace-cmd restore has been broken for some time. This series
fixes it.

Changes since v1:

 - Have tracecmd_read_headers() pass in the state to stop at.
   It can also be called multiple times and it will continue where
   it left off.

 - tracecmd_copy_headers() now takes a start and end state, to
   allow it to be called more than once (and uses tracecmd_read_headers()
   ability to be called more than once and restart where it left off)

 - tracecmd_get_file_state() returns an enum and not long.


Steven Rostedt (VMware) (9):
      trace-cmd restore: Fix to add saved cmdlines after calling tracecmd_create_init_file_override()
      trace-cmd: Move tracecmd_write_cmdlines() out of tracecmd_append_cpu_data()
      trace-cmd: Move the output state updates into the functions that change the state
      trace-cmd: Move the input state updates into the functions that change the state
      trace-cmd input: Validate the input handle when copying from it
      trace-cmd: Have tracecmd_read_headers() specify the state to read up to
      trace-cmd: Have tracecmd_get_file_state() return the enum
      trace-cmd input: Add validation updates to the copy of a handle
      trace-cmd: Have tracecmd_copy_headers() have a start and stop state

----
 lib/trace-cmd/include/private/trace-cmd-private.h |  13 +-
 lib/trace-cmd/trace-input.c                       | 229 +++++++++++++++++++---
 lib/trace-cmd/trace-output.c                      | 113 +++++++----
 tracecmd/trace-hist.c                             |   2 +-
 tracecmd/trace-mem.c                              |   2 +-
 tracecmd/trace-read.c                             |   2 +-
 tracecmd/trace-record.c                           |   3 +
 tracecmd/trace-restore.c                          |   4 +-
 tracecmd/trace-split.c                            |   4 +
 tracecmd/trace-stream.c                           |   2 +-
 10 files changed, 292 insertions(+), 82 deletions(-)

             reply	other threads:[~2021-03-05 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 22:52 Steven Rostedt [this message]
2021-03-05 22:52 ` [PATCH 1/9 v2] trace-cmd restore: Fix to add saved cmdlines after calling tracecmd_create_init_file_override() Steven Rostedt
2021-03-05 22:52 ` [PATCH 2/9 v2] trace-cmd: Move tracecmd_write_cmdlines() out of tracecmd_append_cpu_data() Steven Rostedt
2021-03-05 22:52 ` [PATCH 3/9 v2] trace-cmd: Move the output state updates into the functions that change the state Steven Rostedt
2021-03-05 22:52 ` [PATCH 4/9 v2] trace-cmd: Move the input " Steven Rostedt
2021-03-05 22:52 ` [PATCH 5/9 v2] trace-cmd input: Validate the input handle when copying from it Steven Rostedt
2021-03-05 22:52 ` [PATCH 6/9 v2] trace-cmd: Have tracecmd_read_headers() specify the state to read up to Steven Rostedt
2021-03-05 22:52 ` [PATCH 7/9 v2] trace-cmd: Have tracecmd_get_file_state() return the enum Steven Rostedt
2021-03-05 22:52 ` [PATCH 8/9 v2] trace-cmd input: Add validation updates to the copy of a handle Steven Rostedt
2021-03-05 22:52 ` [PATCH 9/9 v2] trace-cmd: Have tracecmd_copy_headers() have a start and stop state 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=20210305225223.794554327@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.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).