From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: sunliming <sunliming@kylinos.cn>
Cc: beaub@linux.microsoft.com, rostedt@goodmis.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kelulanainsley@gmail.com
Subject: Re: [PATCH v3 0/4] tracing/user_events: Add empty arguments events
Date: Wed, 7 Jun 2023 23:10:23 +0900 [thread overview]
Message-ID: <20230607231023.6097c4c1060d82c74a4cbfee@kernel.org> (raw)
In-Reply-To: <20230606062027.1008398-1-sunliming@kylinos.cn>
On Tue, 6 Jun 2023 14:20:23 +0800
sunliming <sunliming@kylinos.cn> wrote:
> This series patches fix the incorrect trace record for empty arguments
> events and add correspondent selftests.
Looks good for me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
for the series.
>
> V3:
> Improve modification descriptions to maintain consistent formatting
>
> v2:
> Change "i->count" to "i->count !=0 " to prevent compiler optimization
> Add correspondent selftests
>
> sunliming (4):
> tracing/user_events: Fix the incorrect trace record for empty
> arguments events
> selftests/user_events: Add ftrace self-test for empty arguments events
> selftests/user_events: Clear the events after perf self-test
> selftests/user_events: Add perf self-test for empty arguments events
>
> kernel/trace/trace_events_user.c | 4 +-
> .../selftests/user_events/ftrace_test.c | 33 ++++++++
> .../testing/selftests/user_events/perf_test.c | 82 +++++++++++++++++++
> 3 files changed, 117 insertions(+), 2 deletions(-)
>
> --
> 2.25.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-06-07 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 6:20 [PATCH v3 0/4] tracing/user_events: Add empty arguments events sunliming
2023-06-06 6:20 ` [PATCH v3 1/4] tracing/user_events: Fix the incorrect trace record for " sunliming
2023-06-06 6:20 ` [PATCH v3 2/4] selftests/user_events: Add ftrace self-test " sunliming
2023-06-06 6:20 ` [PATCH v3 3/4] selftests/user_events: Clear the events after perf self-test sunliming
2023-06-06 6:20 ` [PATCH v3 4/4] selftests/user_events: Add perf self-test for empty arguments events sunliming
2023-06-06 18:53 ` [PATCH v3 0/4] tracing/user_events: Add " Beau Belgrave
2023-06-07 14:10 ` Masami Hiramatsu [this message]
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=20230607231023.6097c4c1060d82c74a4cbfee@kernel.org \
--to=mhiramat@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=kelulanainsley@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=sunliming@kylinos.cn \
/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).