From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Tianchen Ding <dtcccc@linux.alibaba.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
bpf@vger.kernel.org, kgraul@linux.ibm.com, wenjia@linux.ibm.com,
jaka@linux.ibm.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, pabeni@redhat.com,
song@kernel.org, sdf@google.com, haoluo@google.com, yhs@fb.com,
edumazet@google.com, john.fastabend@gmail.com,
kpsingh@kernel.org, jolsa@kernel.org, guwen@linux.alibaba.com
Subject: Re: [PATCH bpf-next 4/4] bpf/selftests: add simple selftest for bpf_smc_ops
Date: Thu, 24 Oct 2024 13:49:35 +0800 [thread overview]
Message-ID: <a5843fac-c6d3-40f2-b2cb-7bbfde93365e@linux.alibaba.com> (raw)
In-Reply-To: <284e3cb9-9f27-413c-9c05-f017171fa40e@linux.alibaba.com>
On 10/24/24 12:49 PM, Tianchen Ding wrote:
> On 2024/10/24 12:04, D. Wythe wrote:
>>
>>
>> On 10/24/24 10:42 AM, D. Wythe wrote:
>>> From: "D. Wythe" <alibuda@linux.alibaba.com>
>>>
>>> This PATCH adds a tiny selftest for bpf_smc_ops, to verify the ability
>>> to attach and write access.
>>>
>>> Follow the steps below to run this test.
>>>
>>> make -C tools/testing/selftests/bpf
>>> cd tools/testing/selftests/bpf
>>> sudo ./test_progs -t smc
>>>
>>> Results shows:
>>> Summary: 1/1 PASSED, 0 SKIPPED, 0 FAILED
>>
>>
>> Sorry for just found an issue with vary config. I will fix this issues
>> in the next version.
>>
>> D. Wythe
>
> This doesn't build with !CONFIG_SMC.
>
> Maybe you should create an individual dir. (like what sched_ext does)
It's true, I do intend to create an individual dir, and send the patches for
BPF and SMC separately. Thanks for your advises.
Best wishes,
D. Wythe
next prev parent reply other threads:[~2024-10-24 5:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 2:42 [PATCH bpf-next 0/4] net/smc: Introduce smc_bpf_ops D. Wythe
2024-10-24 2:42 ` [PATCH bpf-next 1/4] bpf: export necessary sympols for modules D. Wythe
2024-10-24 2:42 ` [PATCH bpf-next 2/4] bpf: allow to access bpf_prog during bpf_struct_access D. Wythe
2024-10-25 9:14 ` kernel test robot
2024-10-25 12:20 ` kernel test robot
2024-10-24 2:42 ` [PATCH net-next 3/4] net/smc: Introduce smc_bpf_ops D. Wythe
2024-10-25 0:26 ` Martin KaFai Lau
2024-10-25 11:05 ` D. Wythe
2024-10-25 18:30 ` Martin KaFai Lau
2024-10-29 8:53 ` D. Wythe
2024-10-24 2:42 ` [PATCH bpf-next 4/4] bpf/selftests: add simple selftest for bpf_smc_ops D. Wythe
2024-10-24 4:04 ` D. Wythe
2024-10-24 4:49 ` Tianchen Ding
2024-10-24 5:49 ` D. Wythe [this message]
2024-11-03 13:01 ` Zhu Yanjun
2024-11-21 2:00 ` D. Wythe
2024-11-25 10:52 ` Zhu Yanjun
2024-11-25 23:32 ` Martin KaFai Lau
2024-11-26 8:29 ` Zhu Yanjun
2024-11-29 4:11 ` D. Wythe
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=a5843fac-c6d3-40f2-b2cb-7bbfde93365e@linux.alibaba.com \
--to=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dtcccc@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=jaka@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kgraul@linux.ibm.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=wenjia@linux.ibm.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