The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kalesh Singh <kaleshsingh@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: surenb@google.com, hridya@google.com, namhyung@kernel.org,
	kernel-team@android.com, rostedt@goodmis.org,
	mhiramat@kernel.org, Kalesh Singh <kaleshsingh@google.com>,
	Ingo Molnar <mingo@redhat.com>, Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH v2 0/2] tracing/kselftest: histogram trigger expression tests
Date: Thu, 28 Oct 2021 12:57:56 -0700	[thread overview]
Message-ID: <20211028195805.2684854-1-kaleshsingh@google.com> (raw)

This series adds kselftest for histogram trigger expressions and is
dependent on the series at [1] and can be applied on top of those after
dropping the patch 7 in [1].

This version drops the changes to reset_trigger_file().

[1] https://lore.kernel.org/r/20211025200852.3002369-1-kaleshsingh@google.com/

Kalesh Singh (2):
  tracing/histogram: Document hist trigger variables (v2)
  tracing/selftests: Add tests for hist trigger expression parsing (v6)

 kernel/trace/trace.c                          | 11 ++++
 .../trigger/trigger-hist-expressions.tc       | 65 +++++++++++++++++++
 2 files changed, 76 insertions(+)
 create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-expressions.tc

-- 
2.33.0.1079.g6e70778dc9-goog


             reply	other threads:[~2021-10-28 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 19:57 Kalesh Singh [this message]
2021-10-28 19:57 ` [PATCH v2 1/2] tracing/histogram: Document hist trigger variables Kalesh Singh
2021-10-28 19:57 ` [PATCH v6 2/2] tracing/selftests: Add tests for hist trigger expression parsing Kalesh Singh
2021-10-29  5:27   ` 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=20211028195805.2684854-1-kaleshsingh@google.com \
    --to=kaleshsingh@google.com \
    --cc=hridya@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=surenb@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