mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eduardo Mucelli Rezende Oliveira <edumucelli@gmail.com>
To: mhiramat@kernel.org
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] tools/bootconfig: Preserve tracing settings across export and replay
Date: Sun, 22 Nov 2026 01:34:57 +0100	[thread overview]
Message-ID: <cover.1795307698.git.edumucelli@gmail.com> (raw)

Hi Masami,

Thanks for reviewing the earlier bootconfig fixes. I found two more cases
where a tracefs export loses a setting when you use it again. The graph
depth is exported under a name the kernel doesn't recognize at boot, and
an all-f CPU mask is left out entirely.

I checked the rendered kernel command line and exercised export and replay
on my Ubuntu machine using a tracefs fixture. The series is based on
bootconfig/core, including the earlier CPU mask quoting fix.

Thanks,
Eduardo

Eduardo Mucelli Rezende Oliveira (2):
  tools/bootconfig: Use the registered global tracing parameter names
  tools/bootconfig: Preserve all-f tracing CPU masks on export

 Documentation/trace/boottime-trace.rst   |  8 ++++----
 tools/bootconfig/scripts/bconf2ftrace.sh | 21 ++++++++++++++++-----
 tools/bootconfig/scripts/ftrace2bconf.sh |  9 ++++-----
 3 files changed, 24 insertions(+), 14 deletions(-)


base-commit: 0ad31c3252d4c626a93ae6251340ef86b18342d0
-- 
2.53.0


             reply	other threads:[~2026-11-22  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-22  0:34 Eduardo Mucelli Rezende Oliveira [this message]
2026-11-22  0:34 ` [PATCH 1/2] tools/bootconfig: Use the registered global tracing parameter names Eduardo Mucelli Rezende Oliveira
2026-11-22  0:34 ` [PATCH 2/2] tools/bootconfig: Preserve all-f tracing CPU masks on export Eduardo Mucelli Rezende Oliveira

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=cover.1795307698.git.edumucelli@gmail.com \
    --to=edumucelli@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --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

all inboxes | Powered by JetHome®