BPF List
 help / color / mirror / Atom feed
From: Kui-Feng Lee <sinquersw@gmail.com>
To: Martin KaFai Lau <martin.lau@linux.dev>, thinker.li@gmail.com
Cc: kuifeng@meta.com, netdev@vger.kernel.org, bpf@vger.kernel.org,
	ast@kernel.org, song@kernel.org, kernel-team@meta.com,
	andrii@kernel.org, drosen@google.com
Subject: Re: [PATCH bpf-next v16 11/14] bpf, net: switch to dynamic registration
Date: Fri, 19 Jan 2024 11:29:54 -0800	[thread overview]
Message-ID: <bcf6ac83-d1c7-412c-ad82-619c76375c63@gmail.com> (raw)
In-Reply-To: <be69cc3f-0ded-4c7e-8709-1602807d1914@linux.dev>



On 1/18/24 14:25, Martin KaFai Lau wrote:
> On 1/17/24 5:49 PM, thinker.li@gmail.com wrote:
>> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
>> index 1cfbb89944c5..a2522fcfe57c 100644
>> --- a/include/linux/bpf.h
>> +++ b/include/linux/bpf.h
>> @@ -1700,10 +1700,22 @@ struct bpf_struct_ops_common_value {
>>       enum bpf_struct_ops_state state;
>>   };
>> +/* This macro helps developer to register a struct_ops type and generate
>> + * type information correctly. Developers should use this macro to 
>> register
>> + * a struct_ops type instead of calling register_bpf_struct_ops() 
>> directly.
>> + */
>> +#define REGISTER_BPF_STRUCT_OPS(st_ops, type)                \
> 
> One final nit on this macro. Rename this to register_bpf_struct_ops 
> since it is the one will be used a lot, so give it an easier typing name.
> 
>> +    ({                                \
>> +        struct bpf_struct_ops_##type {                \
>> +            struct bpf_struct_ops_common_value common;    \
>> +            struct type data ____cacheline_aligned_in_smp;    \
>> +        };                            \
>> +        BTF_TYPE_EMIT(struct bpf_struct_ops_##type);        \
>> +        register_bpf_struct_ops(st_ops);            \
> 
> and rename this to __register_bpf_struct_ops. Thanks.

Sure!

> 
>> +    })
>> +
>>   #if defined(CONFIG_BPF_JIT) && defined(CONFIG_BPF_SYSCALL)
>>   #define BPF_MODULE_OWNER ((void *)((0xeB9FUL << 2) + 
>> POISON_POINTER_DELTA))
>> -const struct bpf_struct_ops_desc *bpf_struct_ops_find(struct btf 
>> *btf, u32 type_id);
>> -void bpf_struct_ops_init(struct btf *btf, struct bpf_verifier_log *log);
>>   bool bpf_struct_ops_get(const void *kdata);
>>   void bpf_struct_ops_put(const void *kdata);
>>   int bpf_struct_ops_map_sys_lookup_elem(struct bpf_map *map, void *key,
>> @@ -1745,16 +1757,11 @@ struct bpf_dummy_ops {
>>   int bpf_struct_ops_test_run(struct bpf_prog *prog, const union 
>> bpf_attr *kattr,
>>                   union bpf_attr __user *uattr);
>>   #endif
>> +int bpf_struct_ops_desc_init(struct bpf_struct_ops_desc *st_ops_desc,
>> +                 struct btf *btf,
>> +                 struct bpf_verifier_log *log);
>>   void bpf_map_struct_ops_info_fill(struct bpf_map_info *info, struct 
>> bpf_map *map);
>>   #else
>> -static inline const struct bpf_struct_ops_desc 
>> *bpf_struct_ops_find(struct btf *btf, u32 type_id)
>> -{
>> -    return NULL;
>> -}
>> -static inline void bpf_struct_ops_init(struct btf *btf,
>> -                       struct bpf_verifier_log *log)
>> -{
>> -}
>>   static inline bool bpf_try_module_get(const void *data, struct 
>> module *owner)
>>   {
>>       return try_module_get(owner);
>> @@ -1769,6 +1776,10 @@ static inline int 
>> bpf_struct_ops_map_sys_lookup_elem(struct bpf_map *map,
>>   {
>>       return -EINVAL;
>>   }
>> +static inline int bpf_struct_ops_link_create(union bpf_attr *attr)
>> +{
>> +    return -EOPNOTSUPP;
>> +}
> 
> This is added back here which was removed in patch 3...
> 
> Others lgtm.
> 

  reply	other threads:[~2024-01-19 19:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  1:49 [PATCH bpf-next v16 00/14] Registrating struct_ops types from modules thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 01/14] bpf: refactory struct_ops type initialization to a function thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 02/14] bpf: get type information with BTF_ID_LIST thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 03/14] bpf, net: introduce bpf_struct_ops_desc thinker.li
2024-01-18 21:30   ` Martin KaFai Lau
2024-01-19  0:47     ` Kui-Feng Lee
2024-01-18  1:49 ` [PATCH bpf-next v16 04/14] bpf: add struct_ops_tab to btf thinker.li
2024-01-18 21:36   ` Martin KaFai Lau
2024-01-19  1:13     ` Kui-Feng Lee
2024-01-18  1:49 ` [PATCH bpf-next v16 05/14] bpf: make struct_ops_map support btfs other than btf_vmlinux thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 06/14] bpf: pass btf object id in bpf_map_info thinker.li
2024-01-18 21:42   ` Martin KaFai Lau
2024-01-19 21:38     ` Kui-Feng Lee
2024-01-18  1:49 ` [PATCH bpf-next v16 07/14] bpf: lookup struct_ops types from a given module BTF thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 08/14] bpf: pass attached BTF to the bpf_struct_ops subsystem thinker.li
2024-01-18 21:56   ` Martin KaFai Lau
2024-01-19 18:05     ` Kui-Feng Lee
2024-01-19 18:43       ` Kui-Feng Lee
2024-01-18  1:49 ` [PATCH bpf-next v16 09/14] bpf: hold module refcnt in bpf_struct_ops map creation and prog verification thinker.li
2024-01-18 22:18   ` Martin KaFai Lau
2024-01-19 19:10     ` Kui-Feng Lee
2024-01-18  1:49 ` [PATCH bpf-next v16 10/14] bpf: validate value_type thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 11/14] bpf, net: switch to dynamic registration thinker.li
2024-01-18 22:25   ` Martin KaFai Lau
2024-01-19 19:29     ` Kui-Feng Lee [this message]
2024-01-18  1:49 ` [PATCH bpf-next v16 12/14] libbpf: Find correct module BTFs for struct_ops maps and progs thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 13/14] bpf: export btf_ctx_access to modules thinker.li
2024-01-18  1:49 ` [PATCH bpf-next v16 14/14] selftests/bpf: test case for register_bpf_struct_ops() thinker.li
2024-01-18 22:41   ` Martin KaFai Lau
2024-01-19 19:31     ` Kui-Feng Lee

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=bcf6ac83-d1c7-412c-ad82-619c76375c63@gmail.com \
    --to=sinquersw@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=drosen@google.com \
    --cc=kernel-team@meta.com \
    --cc=kuifeng@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=thinker.li@gmail.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