From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Vincent Donnefort <vdonnefort@google.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, kernel-team@android.com,
Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v11 5/5] ring-buffer/selftest: Add ring-buffer mapping test
Date: Sun, 14 Jan 2024 11:20:14 -0500 [thread overview]
Message-ID: <20240114112014.7503163f@rorschach.local.home> (raw)
In-Reply-To: <20240114231711.0959180366d8823dd8543241@kernel.org>
On Sun, 14 Jan 2024 23:17:11 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> >
> > Looks good to me and tested.
> >
> > Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > Tested-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Sorry, I should cancel these. I found this test did not pass if I set
> the function tracer on.
>
> / # cd /sys/kernel/tracing/
> /sys/kernel/tracing # echo function > current_tracer
> /sys/kernel/tracing # /mnt/map_test
> TAP version 13
> 1..2
> # Starting 2 tests from 2 test cases.
> # RUN map.subbuf_size_4k.meta_page_check ...
> # map_test.c:174:meta_page_check:Expected self->meta->entries (15293) == 16 (16)
> # meta_page_check: Test terminated by assertion
> # FAIL map.subbuf_size_4k.meta_page_check
> not ok 1 map.subbuf_size_4k.meta_page_check
> # RUN map.subbuf_size_8k.meta_page_check ...
> # map_test.c:174:meta_page_check:Expected self->meta->entries (15270) == 16 (16)
> # meta_page_check: Test terminated by assertion
> # FAIL map.subbuf_size_8k.meta_page_check
> not ok 2 map.subbuf_size_8k.meta_page_check
> # FAILED: 0 / 2 tests passed.
> # Totals: pass:0 fail:2 xfail:0 xpass:0 skip:0 error:0
>
> Does this depend on "nop" tracer?
Yes.
> > > +
> > > +static int tracefs_reset(void)
> > > +{
> > > + if (__tracefs_write_int(TRACEFS_ROOT"/tracing_on", 0))
> > > + return -1;
> > > + if (__tracefs_write_int(TRACEFS_ROOT"/trace", 0))
> > > + return -1;
> > > + if (__tracefs_write(TRACEFS_ROOT"/set_event", ""))
> > > + return -1;
Looks like the below is needed:
if (__traces_write(TRACEFS_ROOT"/current_tracer", "nop"))
return -1;
> > > +
> > > + return 0;
> > > +}
> > > +
-- Steve
prev parent reply other threads:[~2024-01-14 16:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 16:17 [PATCH v11 0/5] Introducing trace buffer mapping by user-space Vincent Donnefort
2024-01-11 16:17 ` [PATCH v11 1/5] ring-buffer: Zero ring-buffer sub-buffers Vincent Donnefort
2024-01-13 13:38 ` Masami Hiramatsu
2024-01-11 16:17 ` [PATCH v11 2/5] ring-buffer: Introducing ring-buffer mapping functions Vincent Donnefort
2024-01-11 16:34 ` Mathieu Desnoyers
2024-01-11 23:23 ` Steven Rostedt
2024-01-12 9:13 ` Vincent Donnefort
2024-01-12 15:06 ` Steven Rostedt
2024-01-12 15:58 ` Steven Rostedt
2024-01-15 4:43 ` Masami Hiramatsu
2024-01-15 15:37 ` Vincent Donnefort
2024-01-15 16:09 ` Steven Rostedt
2024-01-15 16:23 ` Steven Rostedt
2024-01-15 17:29 ` Vincent Donnefort
2024-01-15 18:03 ` Steven Rostedt
2024-01-15 23:48 ` Masami Hiramatsu
2024-01-11 16:17 ` [PATCH v11 3/5] tracing: Allow user-space mapping of the ring-buffer Vincent Donnefort
2024-01-11 16:17 ` [PATCH v11 4/5] Documentation: tracing: Add ring-buffer mapping Vincent Donnefort
2024-01-13 13:36 ` Masami Hiramatsu
2024-01-14 14:26 ` Masami Hiramatsu
2024-01-14 16:23 ` Steven Rostedt
2024-01-14 23:10 ` Masami Hiramatsu
2024-01-11 16:17 ` [PATCH v11 5/5] ring-buffer/selftest: Add ring-buffer mapping test Vincent Donnefort
2024-01-13 13:39 ` Masami Hiramatsu
2024-01-14 14:17 ` Masami Hiramatsu
2024-01-14 16:20 ` Steven Rostedt [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=20240114112014.7503163f@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vdonnefort@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
all inboxes | Powered by JetHome®