From: Steven Rostedt <rostedt@goodmis.org>
To: Vincent Donnefort <vdonnefort@google.com>
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: Thu, 19 Feb 2026 09:36:05 -0500 [thread overview]
Message-ID: <20260219093605.192fdb48@gandalf.local.home> (raw)
In-Reply-To: <aYtUqOw8SdX7gqZT@google.com>
On Tue, 10 Feb 2026 15:54:16 +0000
Vincent Donnefort <vdonnefort@google.com> wrote:
> 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.
Yeah, I guess I was running the old tests. With the new tests I now have:
tools/testing/selftests/ftrace# ./ftracetest test.d/remotes/
=== 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 [PASS]
[9] Test trace remote non-consuming read [PASS]
[10] Test trace remote unloading [PASS]
# of passed: 5
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 5
# of xfailed: 0
# of undefined(test bug): 0
-- Steve
next prev parent reply other threads:[~2026-02-19 14:36 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
2026-02-19 14:36 ` Steven Rostedt [this message]
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=20260219093605.192fdb48@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=skhan@linuxfoundation.org \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.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