BPF List
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	yonghong.song@linux.dev, tj@kernel.org, memxor@gmail.com
Subject: Re: [PATCH] bpf: make perf_event_read_output accessible from BPF core when available
Date: Mon, 17 Mar 2025 10:58:58 +0100	[thread overview]
Message-ID: <Z9fyYuJgQ-D8q87E@krava> (raw)
In-Reply-To: <20250316180103.12386-1-emil@etsalapatis.com>

On Sun, Mar 16, 2025 at 02:01:03PM -0400, Emil Tsalapatis wrote:
> The perf_event_read_event_output helper is currently only available to
> tracing protrams, but is useful for other BPF programs like sched_ext
> schedulers. When the helper is available, provide its bpf_func_proto
> directly from the bpf core.

please add bpf-next to the subject, otherwise lgtm

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

jirka


> 
> Signed-off-by: Emil Tsalapatis (Meta) <emil@etsalapatis.com>
> ---
>  include/linux/bpf.h      | 2 ++
>  kernel/bpf/core.c        | 5 +++++
>  kernel/bpf/helpers.c     | 2 ++
>  kernel/trace/bpf_trace.c | 5 +++++
>  4 files changed, 14 insertions(+)
> 
> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
> index 0d7b70124d81..973a88d9b52b 100644
> --- a/include/linux/bpf.h
> +++ b/include/linux/bpf.h
> @@ -2059,6 +2059,8 @@ int bpf_prog_calc_tag(struct bpf_prog *fp);
>  const struct bpf_func_proto *bpf_get_trace_printk_proto(void);
>  const struct bpf_func_proto *bpf_get_trace_vprintk_proto(void);
>  
> +const struct bpf_func_proto *bpf_get_perf_event_read_value_proto(void);
> +
>  typedef unsigned long (*bpf_ctx_copy_t)(void *dst, const void *src,
>  					unsigned long off, unsigned long len);
>  typedef u32 (*bpf_convert_ctx_access_t)(enum bpf_access_type type,
> diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
> index 62cb9557ad3b..ba6b6118cf50 100644
> --- a/kernel/bpf/core.c
> +++ b/kernel/bpf/core.c
> @@ -2972,6 +2972,11 @@ const struct bpf_func_proto * __weak bpf_get_trace_vprintk_proto(void)
>  	return NULL;
>  }
>  
> +const struct bpf_func_proto * __weak bpf_get_perf_event_read_value_proto(void)
> +{
> +	return NULL;
> +}
> +
>  u64 __weak
>  bpf_event_output(struct bpf_map *map, u64 flags, void *meta, u64 meta_size,
>  		 void *ctx, u64 ctx_size, bpf_ctx_copy_t ctx_copy)
> diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c
> index 5449756ba102..ddaa41a70676 100644
> --- a/kernel/bpf/helpers.c
> +++ b/kernel/bpf/helpers.c
> @@ -2056,6 +2056,8 @@ bpf_base_func_proto(enum bpf_func_id func_id, const struct bpf_prog *prog)
>  		return &bpf_task_pt_regs_proto;
>  	case BPF_FUNC_trace_vprintk:
>  		return bpf_get_trace_vprintk_proto();
> +	case BPF_FUNC_perf_event_read_value:
> +		return bpf_get_perf_event_read_value_proto();
>  	default:
>  		return NULL;
>  	}
> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> index 13bef2462e94..6b07fa7081d9 100644
> --- a/kernel/trace/bpf_trace.c
> +++ b/kernel/trace/bpf_trace.c
> @@ -607,6 +607,11 @@ static const struct bpf_func_proto bpf_perf_event_read_value_proto = {
>  	.arg4_type	= ARG_CONST_SIZE,
>  };
>  
> +const struct bpf_func_proto *bpf_get_perf_event_read_value_proto(void)
> +{
> +	return &bpf_perf_event_read_value_proto;
> +}
> +
>  static __always_inline u64
>  __bpf_perf_event_output(struct pt_regs *regs, struct bpf_map *map,
>  			u64 flags, struct perf_raw_record *raw,
> -- 
> 2.47.1
> 
> 

      reply	other threads:[~2025-03-17  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16 18:01 [PATCH] bpf: make perf_event_read_output accessible from BPF core when available Emil Tsalapatis
2025-03-17  9:58 ` Jiri Olsa [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=Z9fyYuJgQ-D8q87E@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=emil@etsalapatis.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=tj@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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