From: patchwork-bot+netdevbpf@kernel.org
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
bpf@vger.kernel.org, kernel-team@cloudflare.com
Subject: Re: [PATCH bpf v2 1/1] lib: bpf: tracing: fail compilation if target arch is missing
Date: Thu, 17 Jun 2021 04:20:03 +0000 [thread overview]
Message-ID: <162390360380.962.14577274135893714325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210616083635.11434-1-lmb@cloudflare.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 16 Jun 2021 09:36:35 +0100 you wrote:
> bpf2go is the Go equivalent of libbpf skeleton. The convention is that
> the compiled BPF is checked into the repository to facilitate distributing
> BPF as part of Go packages. To make this portable, bpf2go by default
> generates both bpfel and bpfeb variants of the C.
>
> Using bpf_tracing.h is inherently non-portable since the fields of
> struct pt_regs differ between platforms, so CO-RE can't help us here.
> The only way of working around this is to compile for each target
> platform independently. bpf2go can't do this by default since there
> are too many platforms.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/1] lib: bpf: tracing: fail compilation if target arch is missing
https://git.kernel.org/bpf/bpf-next/c/4a638d581a7a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-06-17 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 8:36 [PATCH bpf v2 1/1] lib: bpf: tracing: fail compilation if target arch is missing Lorenz Bauer
2021-06-17 4:20 ` patchwork-bot+netdevbpf [this message]
2021-06-17 4:24 ` Andrii Nakryiko
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=162390360380.962.14577274135893714325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@cloudflare.com \
--cc=lmb@cloudflare.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