linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, akpm@linux-foundation.org,
	zwisler@google.com, chinglinyu@google.com
Subject: [PATCH 0/4] tracing/histogram: Some fixes for new stacktrace variables
Date: Fri, 10 Feb 2023 15:33:02 -0600	[thread overview]
Message-ID: <cover.1676063532.git.zanussi@kernel.org> (raw)

Hi Steve,

Here are a few fixes for some problems I saw when playing around
with the new stacktrace variable/synthetic event patches.

Thanks,

Tom

Tom Zanussi (4):
  tracing/histogram: Don't use strlen to find length of stacktrace
    variables
  tracing/histogram: Fix a few problems with stacktrace variable
    printing
  tracing/histogram: Fix stacktrace key
  tracing/histogram: Fix stacktrace histogram Documententation

 Documentation/trace/histogram.rst | 156 +++++++++++++++++-------------
 kernel/trace/trace_events_hist.c  |  72 +++++++++++---
 kernel/trace/trace_events_synth.c |   7 +-
 3 files changed, 153 insertions(+), 82 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-02-10 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 21:33 Tom Zanussi [this message]
2023-02-10 21:33 ` [PATCH 1/4] tracing/histogram: Don't use strlen to find length of stacktrace variables Tom Zanussi
2023-02-13 15:24   ` Masami Hiramatsu
2023-02-13 15:56     ` Steven Rostedt
2023-02-10 21:33 ` [PATCH 2/4] tracing/histogram: Fix a few problems with stacktrace variable printing Tom Zanussi
2023-02-10 21:33 ` [PATCH 3/4] tracing/histogram: Fix stacktrace key Tom Zanussi
2023-02-10 23:07   ` kernel test robot
2023-02-10 21:33 ` [PATCH 4/4] tracing/histogram: Fix stacktrace histogram Documententation Tom Zanussi

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.1676063532.git.zanussi@kernel.org \
    --to=zanussi@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chinglinyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=zwisler@google.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).