From: patchwork-bot+netdevbpf@kernel.org
To: Mykola Lysenko <mykolal@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, yhs@fb.com
Subject: Re: [PATCH v4 bpf-next 0/3] BPF test_progs tests improvement
Date: Wed, 09 Mar 2022 01:50:10 +0000 [thread overview]
Message-ID: <164679061042.16054.7847681903762449527.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220308200449.1757478-1-mykolal@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 8 Mar 2022 12:04:46 -0800 you wrote:
> First patch reduces the sample_freq to 1000 to ensure test will
> work even when kernel.perf_event_max_sample_rate was reduced to 1000.
>
> Patches for send_signal and find_vma tune the test implementation to
> make sure needed thread is scheduled. Also, both tests will finish as
> soon as possible after the test condition is met.
>
> [...]
Here is the summary with links:
- [v4,bpf-next,1/3] Improve perf related BPF tests (sample_freq issue)
https://git.kernel.org/bpf/bpf-next/c/d4b540544499
- [v4,bpf-next,2/3] Improve send_signal BPF test stability
https://git.kernel.org/bpf/bpf-next/c/1fd49864127c
- [v4,bpf-next,3/3] Improve stability of find_vma BPF test
https://git.kernel.org/bpf/bpf-next/c/ba83af059153
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-09 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 20:04 [PATCH v4 bpf-next 0/3] BPF test_progs tests improvement Mykola Lysenko
2022-03-08 20:04 ` [PATCH v4 bpf-next 1/3] Improve perf related BPF tests (sample_freq issue) Mykola Lysenko
2022-03-08 20:04 ` [PATCH v4 bpf-next 2/3] Improve send_signal BPF test stability Mykola Lysenko
2022-03-08 20:04 ` [PATCH v4 bpf-next 3/3] Improve stability of find_vma BPF test Mykola Lysenko
2022-03-09 1:50 ` patchwork-bot+netdevbpf [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=164679061042.16054.7847681903762449527.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=mykolal@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 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.