bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hou Tao <houtao1@huawei.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: Yonghong Song <yhs@fb.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	Martin KaFai Lau <kafai@fb.com>, <netdev@vger.kernel.org>,
	<bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v4 0/3] add support for writable bare tracepoint
Date: Thu, 30 Sep 2021 18:06:49 +0800	[thread overview]
Message-ID: <b6cf9124-f421-bfea-0cee-27307e7fbc07@huawei.com> (raw)
In-Reply-To: <20210930091355.2794601-5-houtao1@huawei.com>

Oops, I mistakenly send out the zero-patch again. Sorry for that.

On 9/30/2021 5:13 PM, Hou Tao wrote:
> Hi,
>
> The patchset series supports writable context for bare tracepoint.
>
> The main idea comes from patchset "writable contexts for bpf raw
> tracepoints" [1], but it only supports normal tracepoint with
> associated trace event under tracefs. Now we have one use case
> in which we will add bare tracepoint in VFS layer, and update
> file::f_mode for specific files. The reason using bare tracepoint
> is that it doesn't form a ABI and we can change it freely. So
> add support for it in BPF.
>
> Comments are always welcome.
>
> [1]: https://lore.kernel.org/lkml/20190426184951.21812-1-mmullins@fb.com
>
> Change log:
> v4:
>  * rebased on bpf-next
>  * patch 2 is updated to add support for writable raw tracepoint
>    attachment in attach_raw_tp().
>
> v3: https://www.spinics.net/lists/bpf/msg46824.html
>   * use raw_tp.w instead of raw_tp_writable as section
>     name of writable tp
>   * use ASSERT_XXX() instead of CHECK()
>   * define a common macro for "/sys/kernel/bpf_testmod"
>
> v2: https://www.spinics.net/lists/bpf/msg46356.html 
>   * rebase on bpf-next tree
>   * address comments from Yonghong Song
>   * rename bpf_testmode_test_writable_ctx::ret as early_ret to reflect
>     its purpose better.
>
> v1: https://www.spinics.net/lists/bpf/msg46221.html
>
> Hou Tao (3):
>   bpf: support writable context for bare tracepoint
>   libbpf: support detecting and attaching of writable tracepoint program
>   bpf/selftests: add test for writable bare tracepoint
>
>  include/trace/bpf_probe.h                     | 19 +++++++---
>  tools/lib/bpf/libbpf.c                        | 21 ++++++++---
>  .../bpf/bpf_testmod/bpf_testmod-events.h      | 15 ++++++++
>  .../selftests/bpf/bpf_testmod/bpf_testmod.c   | 10 ++++++
>  .../selftests/bpf/bpf_testmod/bpf_testmod.h   |  5 +++
>  .../selftests/bpf/prog_tests/module_attach.c  | 35 +++++++++++++++++++
>  .../selftests/bpf/progs/test_module_attach.c  | 14 ++++++++
>  tools/testing/selftests/bpf/test_progs.c      |  4 +--
>  tools/testing/selftests/bpf/test_progs.h      |  2 ++
>  9 files changed, 114 insertions(+), 11 deletions(-)
>


      reply	other threads:[~2021-09-30 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  9:13 Hou Tao
2021-09-30  9:13 ` [PATCH bpf-next v4 1/3] bpf: support writable context for " Hou Tao
2021-10-01 22:21   ` Andrii Nakryiko
2021-09-30  9:13 ` [PATCH bpf-next v4 2/3] libbpf: support detecting and attaching of writable tracepoint program Hou Tao
2021-10-01 22:21   ` Andrii Nakryiko
2021-09-30  9:13 ` [PATCH bpf-next v4 3/3] bpf/selftests: add test for writable bare tracepoint Hou Tao
2021-09-30  9:13 ` [PATCH bpf-next v4 0/3] add support " Hou Tao
2021-09-30 10:06   ` Hou Tao [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=b6cf9124-f421-bfea-0cee-27307e7fbc07@huawei.com \
    --to=houtao1@huawei.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=yhs@fb.com \
    --subject='Re: [PATCH bpf-next v4 0/3] add support for writable bare tracepoint' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).