BPF List
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, eddyz87@gmail.com, mykolal@fb.com,
	kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 1/2] libbpf: implement bpf_usdt_arg_size BPF function
Date: Wed, 26 Feb 2025 15:34:32 +0100	[thread overview]
Message-ID: <Z78meJOKZ1AGsnwl@krava> (raw)
In-Reply-To: <20250224235756.2612606-1-ihor.solodrai@linux.dev>

On Mon, Feb 24, 2025 at 03:57:55PM -0800, Ihor Solodrai wrote:
> Information about USDT argument size is implicitly stored in
> __bpf_usdt_arg_spec, but currently it's not accessbile to BPF programs
> that use USDT.
> 
> Implement bpf_sdt_arg_size() that returns the size of an USDT argument
> in bytes.
> 
> v1->v2:
>   * do not add __bpf_usdt_arg_spec() helper

Reviewed-by: Jiri Olsa <jolsa@kernel.org>

jirka

> 
> v1: https://lore.kernel.org/bpf/20250220215904.3362709-1-ihor.solodrai@linux.dev/
> 
> Suggested-by: Andrii Nakryiko <andrii@kernel.org>
> Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
> ---
>  tools/lib/bpf/usdt.bpf.h | 32 ++++++++++++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
> 
> diff --git a/tools/lib/bpf/usdt.bpf.h b/tools/lib/bpf/usdt.bpf.h
> index b811f754939f..2a7865c8e3fe 100644
> --- a/tools/lib/bpf/usdt.bpf.h
> +++ b/tools/lib/bpf/usdt.bpf.h
> @@ -108,6 +108,38 @@ int bpf_usdt_arg_cnt(struct pt_regs *ctx)
>  	return spec->arg_cnt;
>  }
>  
> +/* Returns the size in bytes of the #*arg_num* (zero-indexed) USDT argument.
> + * Returns negative error if argument is not found or arg_num is invalid.
> + */
> +static __always_inline
> +int bpf_usdt_arg_size(struct pt_regs *ctx, __u64 arg_num)
> +{
> +	struct __bpf_usdt_arg_spec *arg_spec;
> +	struct __bpf_usdt_spec *spec;
> +	int spec_id;
> +
> +	spec_id = __bpf_usdt_spec_id(ctx);
> +	if (spec_id < 0)
> +		return -ESRCH;
> +
> +	spec = bpf_map_lookup_elem(&__bpf_usdt_specs, &spec_id);
> +	if (!spec)
> +		return -ESRCH;
> +
> +	if (arg_num >= BPF_USDT_MAX_ARG_CNT)
> +		return -ENOENT;
> +	barrier_var(arg_num);
> +	if (arg_num >= spec->arg_cnt)
> +		return -ENOENT;
> +
> +	arg_spec = &spec->args[arg_num];
> +
> +	/* arg_spec->arg_bitshift = 64 - arg_sz * 8
> +	 * so: arg_sz = (64 - arg_spec->arg_bitshift) / 8
> +	 */
> +	return (unsigned int)(64 - arg_spec->arg_bitshift) / 8;
> +}
> +
>  /* Fetch USDT argument #*arg_num* (zero-indexed) and put its value into *res.
>   * Returns 0 on success; negative error, otherwise.
>   * On error *res is guaranteed to be set to zero.
> -- 
> 2.48.1
> 
> 

  parent reply	other threads:[~2025-02-26 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 23:57 [PATCH bpf-next v2 1/2] libbpf: implement bpf_usdt_arg_size BPF function Ihor Solodrai
2025-02-24 23:57 ` [PATCH bpf-next v2 2/2] selftests/bpf: test bpf_usdt_arg_size() function Ihor Solodrai
2025-02-26 14:36   ` Jiri Olsa
2025-02-26 14:34 ` Jiri Olsa [this message]
2025-02-26 18:20 ` [PATCH bpf-next v2 1/2] libbpf: implement bpf_usdt_arg_size BPF function patchwork-bot+netdevbpf

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=Z78meJOKZ1AGsnwl@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@meta.com \
    --cc=mykolal@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