public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Rong Tao <rtoax@foxmail.com>
Cc: olsajiri@gmail.com, andrii@kernel.org, ast@kernel.org,
	bpf@vger.kernel.org, daniel@iogearbox.net, haoluo@google.com,
	john.fastabend@gmail.com, kpsingh@kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	martin.lau@linux.dev, mykolal@fb.com, rongtao@cestc.cn,
	sdf@google.com, shuah@kernel.org, song@kernel.org,
	yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v5] selftests/bpf: trace_helpers.c: optimize kallsyms cache
Date: Fri, 18 Aug 2023 14:20:29 +0200	[thread overview]
Message-ID: <ZN9iDSj3/vdk5pRX@krava> (raw)
In-Reply-To: <tencent_03EBFD524265EA7560341E91C5E04F083405@qq.com>

On Fri, Aug 18, 2023 at 09:39:32AM +0800, Rong Tao wrote:
> Hi, Jiri. Thanks for your reply.
> 
> libbpf_ensure_mem() is in libbpf_internal.h, samples/bpf/ can't see it, do we
> reposition the function declaration?

I see, I had no idea trace_helpers.[ch] is included in samples/bpf

but it seems to have libbpf linked statically.. so you could just
include libbpf_internal.h and it should work, right? like we do
in selftests

jirka

> 
> Good Day
> Rong Tao
> 

  reply	other threads:[~2023-08-18 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  5:03 [PATCH bpf-next v5] selftests/bpf: trace_helpers.c: optimize kallsyms cache Rong Tao
2023-08-17  8:21 ` Jiri Olsa
2023-08-18  1:39   ` Rong Tao
2023-08-18 12:20     ` Jiri Olsa [this message]
2023-08-18 15:36       ` Rong Tao
2023-08-18 17:50         ` Yonghong Song
2023-08-21  2:03           ` Rong Tao
2023-08-21  4:34             ` Yonghong Song
2023-08-21  6:49               ` Rong Tao

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=ZN9iDSj3/vdk5pRX@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=rongtao@cestc.cn \
    --cc=rtoax@foxmail.com \
    --cc=sdf@google.com \
    --cc=shuah@kernel.org \
    --cc=song@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