From: Martin KaFai Lau <martin.lau@linux.dev>
To: Hou Tao <houtao@huaweicloud.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Song Liu <songliubraving@fb.com>, Hao Luo <haoluo@google.com>,
Yonghong Song <yhs@fb.com>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
KP Singh <kpsingh@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Jiri Olsa <jolsa@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Lorenz Bauer <oss@lmb.io>,
houtao1@huawei.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Add test result messages for test_task_storage_map_stress_lookup
Date: Mon, 19 Sep 2022 11:25:42 -0700 [thread overview]
Message-ID: <3797ccec-6fe1-acc9-02f0-2f5ee0e8b7d8@linux.dev> (raw)
In-Reply-To: <20220919035714.2195144-1-houtao@huaweicloud.com>
On 9/18/22 8:57 PM, Hou Tao wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Add test result message when test_task_storage_map_stress_lookup()
> succeeds or is skipped. The test case can be skipped due to the choose
> of preemption model in kernel config, so export skips in test_maps.c and
> increase it when needed.
>
> The following is the output of test_maps when the test case succeeds or
> is skipped:
>
> test_task_storage_map_stress_lookup:PASS
> test_maps: OK, 0 SKIPPED
>
> test_task_storage_map_stress_lookup SKIP (no CONFIG_PREEMPT)
> test_maps: OK, 1 SKIPPED
>
> Signed-off-by: Hou Tao <houtao1@huawei.com>
Applied with a Fixes tag,
Fixes: 73b97bc78b32 ("selftests/bpf: ......
Please remember to add it next time for fixes.
Also, ...
> ---
> tools/testing/selftests/bpf/map_tests/task_storage_map.c | 6 +++++-
> tools/testing/selftests/bpf/test_maps.c | 2 +-
> tools/testing/selftests/bpf/test_maps.h | 2 ++
> 3 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/map_tests/task_storage_map.c b/tools/testing/selftests/bpf/map_tests/task_storage_map.c
> index 1adc9c292eb2..aac08c85240b 100644
> --- a/tools/testing/selftests/bpf/map_tests/task_storage_map.c
> +++ b/tools/testing/selftests/bpf/map_tests/task_storage_map.c
> @@ -77,8 +77,11 @@ void test_task_storage_map_stress_lookup(void)
> CHECK(err, "open_and_load", "error %d\n", err);
>
> /* Only for a fully preemptible kernel */
> - if (!skel->kconfig->CONFIG_PREEMPT)
> + if (!skel->kconfig->CONFIG_PREEMPT) {
> + printf("%s SKIP (no CONFIG_PREEMPT)\n", __func__);
> + skips++;
I noticed it is missing a read_bpf_task_storage_busy__destroy() here.
Please fix.
next prev parent reply other threads:[~2022-09-19 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 3:57 [PATCH bpf-next] selftests/bpf: Add test result messages for test_task_storage_map_stress_lookup Hou Tao
2022-09-19 18:20 ` patchwork-bot+netdevbpf
2022-09-19 18:25 ` Martin KaFai Lau [this message]
2022-09-20 1:12 ` Hou Tao
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=3797ccec-6fe1-acc9-02f0-2f5ee0e8b7d8@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=oss@lmb.io \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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