From: Eduardo Mucelli Rezende Oliveira <edumucelli@gmail.com>
To: mhiramat@kernel.org
Cc: rostedt@goodmis.org, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] tools/bootconfig: Fix tracing script filters and histogram dependencies
Date: Sat, 31 Oct 2026 19:35:29 +0100 [thread overview]
Message-ID: <cover.1793471731.git.edumucelli@gmail.com> (raw)
Hi Masami,
Thanks for the reviews and for picking up the previous fixes. Here are
five more script fixes, based on bootconfig/core as you suggested.
They address:
- The documented ftrace.notraces setting being ignored by bconf2ftrace.sh.
- Single quotes in event actions producing invalid exported bootconfig.
- Literal filter text being mistaken for histogram variable syntax.
- Valid histogram dependency chains exceeding the exporter's retry limit.
- Helper key lookups matching unrelated bootconfig keys.
The action-quoting patch follows up on the trigger-filter fix you picked
up. It uses the same warning approach for unrepresentable values that
you suggested for event filters. The histogram scan uses POSIX sed.
I tested the conversion and export fixes in temporary tracefs instances
on my Ubuntu machine, running kernel 7.0.0-38-generic, with recording
disabled. The tests cover each relevant step and the combined series.
The helper fix has focused checks, and all 81 combined fixture checks
also pass with POSIX sed.
Feedback is welcome.
Thanks,
Eduardo
Eduardo Mucelli Rezende Oliveira (5):
tools/bootconfig: Read the documented ftrace.notraces key
tools/bootconfig: Preserve quotes in exported event actions
tools/bootconfig: Ignore filter strings when resolving histogram
variables
tools/bootconfig: Resolve histogram dependencies until no progress is
made
tools/bootconfig: Match literal keys in tracing script helpers
tools/bootconfig/scripts/bconf2ftrace.sh | 2 +-
tools/bootconfig/scripts/ftrace2bconf.sh | 27 ++++++++++++++++++------
tools/bootconfig/scripts/xbc.sh | 13 ++++++++----
3 files changed, 31 insertions(+), 11 deletions(-)
base-commit: a52ceed51e9bf8f1ca9c2c868b14bf6861986c65
--
2.53.0
next reply other threads:[~2026-10-31 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 18:35 Eduardo Mucelli Rezende Oliveira [this message]
2026-10-31 18:35 ` [PATCH 1/5] tools/bootconfig: Read the documented ftrace.notraces key Eduardo Mucelli Rezende Oliveira
2026-10-31 18:35 ` [PATCH 2/5] tools/bootconfig: Preserve quotes in exported event actions Eduardo Mucelli Rezende Oliveira
2026-10-31 18:35 ` [PATCH 3/5] tools/bootconfig: Ignore filter strings when resolving histogram variables Eduardo Mucelli Rezende Oliveira
2026-10-31 18:35 ` [PATCH 4/5] tools/bootconfig: Resolve histogram dependencies until no progress is made Eduardo Mucelli Rezende Oliveira
2026-10-31 18:35 ` [PATCH 5/5] tools/bootconfig: Match literal keys in tracing script helpers 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.1793471731.git.edumucelli@gmail.com \
--to=edumucelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.