public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH] MIPS: Enable some missed configs in loongson3_defconfig to support bpftrace
Date: Wed, 10 Mar 2021 16:09:41 +0100	[thread overview]
Message-ID: <20210310150941.GF12960@alpha.franken.de> (raw)
In-Reply-To: <1615186098-2643-1-git-send-email-yangtiezhu@loongson.cn>

On Mon, Mar 08, 2021 at 02:48:18PM +0800, Tiezhu Yang wrote:
> bpftrace is a high-level tracing language for Linux enhanced Berkeley
> Packet Filter (eBPF) available in recent Linux kernels (4.x). bpftrace
> uses LLVM as a backend to compile scripts to BPF-bytecode and makes use
> of BCC for interacting with the Linux BPF system, as well as existing
> Linux tracing capabilities: kernel dynamic tracing (kprobes), user-level
> dynamic tracing (uprobes), and tracepoints.
> 
> According to Linux Kernel Requirements in bpftrace/INSTALL.md [1], the
> kernel needs to be built with the following options:
> 
> CONFIG_BPF=y
> CONFIG_BPF_SYSCALL=y
> CONFIG_BPF_JIT=y
> CONFIG_HAVE_EBPF_JIT=y
> CONFIG_BPF_EVENTS=y
> CONFIG_FTRACE_SYSCALLS=y
> CONFIG_FUNCTION_TRACER=y
> CONFIG_HAVE_DYNAMIC_FTRACE=y
> CONFIG_DYNAMIC_FTRACE=y
> CONFIG_HAVE_KPROBES=y
> CONFIG_KPROBES=y
> CONFIG_KPROBE_EVENTS=y
> CONFIG_ARCH_SUPPORTS_UPROBES=y
> CONFIG_UPROBES=y
> CONFIG_UPROBE_EVENTS=y
> CONFIG_DEBUG_FS=y
> 
> So enable some missed configs in loongson3_defconfig to make sure
> the above configs are set after make loongson3_defconfig.
> 
> [1] https://github.com/iovisor/bpftrace/blob/master/INSTALL.md
> 
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
>  arch/mips/configs/loongson3_defconfig | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2021-03-10 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08  6:48 [PATCH] MIPS: Enable some missed configs in loongson3_defconfig to support bpftrace Tiezhu Yang
2021-03-10 15:09 ` Thomas Bogendoerfer [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=20210310150941.GF12960@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=yangtiezhu@loongson.cn \
    /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