From: Martin KaFai Lau <[email protected]>
To: Breno Leitao <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected],
"Daniel Müller" <[email protected]>,
"Wang Yufen" <[email protected]>,
"open list:KERNEL SELFTEST FRAMEWORK"
<[email protected]>,
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
"Andrii Nakryiko" <[email protected]>,
"Mykola Lysenko" <[email protected]>,
"Alexei Starovoitov" <[email protected]>,
"Daniel Borkmann" <[email protected]>,
"Song Liu" <[email protected]>,
"Yonghong Song" <[email protected]>,
"John Fastabend" <[email protected]>,
"KP Singh" <[email protected]>, "Hao Luo" <[email protected]>,
"Jiri Olsa" <[email protected]>, "Shuah Khan" <[email protected]>
Subject: Re: [PATCH v6 8/8] selftests/bpf/sockopt: Add io_uring support
Date: Wed, 13 Sep 2023 13:48:09 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/13/23 8:27 AM, Breno Leitao wrote:
> Expand the BPF sockopt test to use also check for io_uring
> {g,s}etsockopt commands operations.
>
> Create infrastructure to run io_uring tests using the mini_liburing
> helpers, so, the {g,s}etsockopt operation could either be called from
> system calls, or, via io_uring.
>
> Add a 'use_io_uring' parameter to run_test(), to specify if the test
> should be run using io_uring if the parameter is set, or via the regular
> system calls if false.
>
> Call *all* tests twice, using the regular io_uring path, and the new
> io_uring path.
The bpf CI failed to compile because of missing some newer enum:
https://github.com/kernel-patches/bpf/actions/runs/6176703557/job/16766325932
An option is to copy the io_uring.h to tools/include/uapi/linux/.
prev parent reply other threads:[~2023-09-13 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 15:27 [PATCH v6 0/8] io_uring: Initial support for {s,g}etsockopt commands Breno Leitao
2023-09-13 15:27 ` [PATCH v6 1/8] net/socket: Break down __sys_setsockopt Breno Leitao
2023-09-13 15:27 ` [PATCH v6 2/8] net/socket: Break down __sys_getsockopt Breno Leitao
2023-09-13 15:27 ` [PATCH v6 3/8] io_uring/cmd: Pass compat mode in issue_flags Breno Leitao
2023-09-13 15:27 ` [PATCH v6 4/8] selftests/net: Extract uring helpers to be reusable Breno Leitao
2023-09-13 15:27 ` [PATCH v6 5/8] io_uring/cmd: return -EOPNOTSUPP if net is disabled Breno Leitao
2023-09-13 15:27 ` [PATCH v6 6/8] io_uring/cmd: Introduce SOCKET_URING_OP_GETSOCKOPT Breno Leitao
2023-09-13 19:36 ` Jens Axboe
2023-09-13 19:37 ` Jens Axboe
2023-09-13 15:27 ` [PATCH v6 7/8] io_uring/cmd: Introduce SOCKET_URING_OP_SETSOCKOPT Breno Leitao
2023-09-13 19:39 ` Jens Axboe
2023-09-13 15:27 ` [PATCH v6 8/8] selftests/bpf/sockopt: Add io_uring support Breno Leitao
2023-09-13 20:48 ` Martin KaFai Lau [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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