public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH 0/6] tools/bootconfig: Add boot-time tracing script
Date: Mon, 10 Aug 2020 17:34:30 +0900	[thread overview]
Message-ID: <159704847064.175360.3292152056631660862.stgit@devnote2> (raw)

Hi,

This is a series of patches to introduce scripts for the boot-time tracing.

- bconf2ftrace.sh generates a shell script from a bootconfig file which
  setup ftrace via tracefs. This is useful for checking whether your
  boot-time tracing bootconfig is working as you expected.

- ftrace2bconf.sh generates a bootconfig file from current ftrace setting.
  You can set up the ftrace manually and run a test on it before dump it
  to a bootconfig file.
  Note that some function-tracer/fgraph-tracer options are not supported
  by ftrace2bconf.sh, because the original wildcard expression has been
  lost during setup ftrace.

Also, this series improve the bootconfig command to increase usability.

- The bootconfig can format the bootconfig file without initrd. You don't
  need a dummy initrd anymore :)
- The bootconfig command supports -l (format as a list) option which
  outputs the bootconfig as a key-value list, as same as /proc/bootconfig.


Thank you,

---

Masami Hiramatsu (6):
      tools/bootconfig: Show bootconfig compact tree from bootconfig file
      tools/bootconfig: Add list option
      tools/bootconfig: Make all functions static
      tools/bootconfig: Add a script to generate ftrace shell-command from bootconfig
      tools/bootconfig: Add a script to generates bootconfig from ftrace
      tools/bootconfig: Add --init option for bconf2ftrace.sh


 tools/bootconfig/main.c                  |  147 +++++++++++++-----
 tools/bootconfig/scripts/bconf2ftrace.sh |  199 ++++++++++++++++++++++++
 tools/bootconfig/scripts/ftrace.sh       |  109 +++++++++++++
 tools/bootconfig/scripts/ftrace2bconf.sh |  244 ++++++++++++++++++++++++++++++
 tools/bootconfig/scripts/xbc.sh          |   56 +++++++
 5 files changed, 713 insertions(+), 42 deletions(-)
 create mode 100755 tools/bootconfig/scripts/bconf2ftrace.sh
 create mode 100644 tools/bootconfig/scripts/ftrace.sh
 create mode 100755 tools/bootconfig/scripts/ftrace2bconf.sh
 create mode 100644 tools/bootconfig/scripts/xbc.sh

--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>

             reply	other threads:[~2020-08-10  8:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  8:34 Masami Hiramatsu [this message]
2020-08-10  8:34 ` [PATCH 1/6] tools/bootconfig: Show bootconfig compact tree from bootconfig file Masami Hiramatsu
2020-08-10  8:34 ` [PATCH 2/6] tools/bootconfig: Add list option Masami Hiramatsu
2020-08-10  8:35 ` [PATCH 3/6] tools/bootconfig: Make all functions static Masami Hiramatsu
2020-08-10  8:35 ` [PATCH 4/6] tools/bootconfig: Add a script to generate ftrace shell-command from bootconfig Masami Hiramatsu
2020-08-14  1:01   ` Steven Rostedt
2020-08-15 10:57     ` Masami Hiramatsu
2020-08-10  8:35 ` [PATCH 5/6] tools/bootconfig: Add a script to generates bootconfig from ftrace Masami Hiramatsu
2020-08-10  8:35 ` [PATCH 6/6] tools/bootconfig: Add --init option for bconf2ftrace.sh Masami Hiramatsu

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=159704847064.175360.3292152056631660862.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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