From: Steven Rostedt <rostedt@goodmis.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Ingo Molnar <mingo@redhat.com>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org, joseph.salisbury@canonical.com,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests/ftrace: Do not trace do_softirq because of PREEMPT_RT
Date: Thu, 10 Feb 2022 10:07:53 -0500 [thread overview]
Message-ID: <20220210100753.27248bf6@gandalf.local.home> (raw)
In-Reply-To: <YgUlybNMlpheddiD@linutronix.de>
On Thu, 10 Feb 2022 15:48:41 +0100
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> After looking into the test it appears that two random functions are
> enough to be specified because the actual purpose is it to figure out if
> the function is recorded and not the actual functionality behind the
> function.
Correct. And if I ever do get a chance to revisit this test, I plan on
adding a bunch of comments to it. It's hard enough to add tests for one's
code, but even harder to document what those tests actually do ;-)
-- Steve
next prev parent reply other threads:[~2022-02-10 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 8:33 [PATCH v2] selftests/ftrace: Do not trace do_softirq because of PREEMPT_RT Krzysztof Kozlowski
2022-02-10 13:47 ` Sebastian Andrzej Siewior
2022-02-10 14:05 ` Krzysztof Kozlowski
2022-02-10 14:10 ` Sebastian Andrzej Siewior
2022-02-10 14:13 ` Krzysztof Kozlowski
2022-02-10 14:48 ` Sebastian Andrzej Siewior
2022-02-10 15:07 ` Steven Rostedt [this message]
2022-02-10 15:05 ` Steven Rostedt
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=20220210100753.27248bf6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=joseph.salisbury@canonical.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.