From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org, maz@kernel.org,
oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
jstultz@google.com, qperret@google.com, will@kernel.org,
aneesh.kumar@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v11 15/30] tracing: selftests: Add trace remote tests
Date: Tue, 10 Feb 2026 15:54:16 +0000 [thread overview]
Message-ID: <aYtUqOw8SdX7gqZT@google.com> (raw)
In-Reply-To: <20260205124208.2ed7cff8@gandalf.local.home>
On Thu, Feb 05, 2026 at 12:42:08PM -0500, Steven Rostedt wrote:
> On Sat, 31 Jan 2026 13:28:33 +0000
> Vincent Donnefort <vdonnefort@google.com> wrote:
>
> > Exercise the tracefs interface for trace remote with a set of tests to
> > check:
> >
> > * loading/unloading (unloading.tc)
> > * reset (reset.tc)
> > * size changes (buffer_size.tc)
> > * consuming read (trace_pipe.tc)
> > * non-consuming read (trace.tc)
> >
> > Cc: Shuah Khan <skhan@linuxfoundation.org>
> > Cc: linux-kselftest@vger.kernel.org
> > Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
>
> This still fails:
>
> === Ftrace unit tests ===
> [1] Test trace remote buffer size [PASS]
> [2] Test hypervisor trace buffer size [UNSUPPORTED]
> [3] Test hypervisor trace buffer reset [UNSUPPORTED]
> [4] Test hypervisor consuming trace read [UNSUPPORTED]
> [5] Test hypervisor non-consuming trace read [UNSUPPORTED]
> [6] Test hypervisor trace buffer unloading [UNSUPPORTED]
> [7] Test trace remote reset [PASS]
> [8] Test trace remote consuming read [FAIL]
> [9] Test trace remote non-consuming read [FAIL]
> [10] Test trace remote unloading [PASS]
>
> I added this patch and the two failed tests now pass:
>
> diff --git a/tools/testing/selftests/ftrace/test.d/remotes/trace.tc b/tools/testing/selftests/ftrace/test.d/remotes/trace.tc
> index 081133ec45ff..dfc954a6a380 100644
> --- a/tools/testing/selftests/ftrace/test.d/remotes/trace.tc
> +++ b/tools/testing/selftests/ftrace/test.d/remotes/trace.tc
> @@ -106,8 +106,10 @@ test_trace()
> echo 0 > trace
>
> for cpu in $(get_cpu_ids); do
> - echo 0 > /sys/devices/system/cpu/cpu$cpu/online
> - break
> + if [ -f /sys/devices/system/cpu/cpu$cpu/online ]; then
> + echo 0 > /sys/devices/system/cpu/cpu$cpu/online
> + break
> + fi
Hum weird, I have changed it in v11 to
echo 0 > /sys/devices/system/cpu/cpu$cpu/online || return 0
That doesn't work? Because I would simply stop the test there if we can't
offline the CPU.
> done
>
> for i in $(seq 1 8); do
> diff --git a/tools/testing/selftests/ftrace/test.d/remotes/trace_pipe.tc b/tools/testing/selftests/ftrace/test.d/remotes/trace_pipe.tc
> index d28eaee10c7c..146f0a9fe311 100644
> --- a/tools/testing/selftests/ftrace/test.d/remotes/trace_pipe.tc
> +++ b/tools/testing/selftests/ftrace/test.d/remotes/trace_pipe.tc
> @@ -102,8 +102,10 @@ test_trace_pipe()
> echo 0 > trace
>
> for cpu in $(get_cpu_ids); do
> - echo 0 > /sys/devices/system/cpu/cpu$cpu/online
> - break
> + if [ -f /sys/devices/system/cpu/cpu$cpu/online ]; then
> + echo 0 > /sys/devices/system/cpu/cpu$cpu/online
> + break
> + fi
> done
>
> for i in $(seq 1 8); do
>
> -- Steve
next prev parent reply other threads:[~2026-02-10 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260131132848.254084-1-vdonnefort@google.com>
2026-01-31 13:28 ` [PATCH v11 15/30] tracing: selftests: Add trace remote tests Vincent Donnefort
2026-02-05 17:42 ` Steven Rostedt
2026-02-10 15:54 ` Vincent Donnefort [this message]
2026-02-19 14:36 ` Steven Rostedt
2026-01-31 13:28 ` [PATCH v11 30/30] tracing: selftests: Add hypervisor " Vincent Donnefort
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=aYtUqOw8SdX7gqZT@google.com \
--to=vdonnefort@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=joey.gouly@arm.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--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=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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