From: Yonghong Song <yhs@fb.com>
To: <bpf@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
Lorenz Bauer <lmb@cloudflare.com>
Subject: Re: [PATCH bpf-next v2] docs/bpf: add llvm_reloc.rst to explain llvm bpf relocations
Date: Tue, 25 May 2021 08:31:23 -0700 [thread overview]
Message-ID: <4392b2d9-9643-00e9-c9fe-f722041adef8@fb.com> (raw)
In-Reply-To: <20210525152500.2061481-1-yhs@fb.com>
sorry, please ignore this one. The same patch has been sent out last
night. I may have accidentally deleted it from my inbox and didn't see
it and so sent out again.
On 5/25/21 8:25 AM, Yonghong Song wrote:
> LLVM upstream commit https://reviews.llvm.org/D102712
> made some changes to bpf relocations to make them
> llvm linker lld friendly. The scope of
> existing relocations R_BPF_64_{64,32} is narrowed
> and new relocations R_BPF_64_{ABS32,ABS64,NODYLD32}
> are introduced.
>
> Let us add some documentation about llvm bpf
> relocations so people can understand how to resolve
> them properly in their respective tools.
>
> Cc: John Fastabend <john.fastabend@gmail.com>
> Cc: Lorenz Bauer <lmb@cloudflare.com>
> Signed-off-by: Yonghong Song <yhs@fb.com>
> ---
> Documentation/bpf/index.rst | 1 +
> Documentation/bpf/llvm_reloc.rst | 240 +++++++++++++++++++++++++
> tools/testing/selftests/bpf/README.rst | 19 ++
> 3 files changed, 260 insertions(+)
> create mode 100644 Documentation/bpf/llvm_reloc.rst
>
> Changelogs:
> v1 -> v2:
> - add an example to illustrate how relocations related to base
> section and symbol table and what is "Implicit Addend"
> - clarify why we use 32bit read/write for R_BPF_64_64 (ld_imm64)
> relocations.
>
[...]
next prev parent reply other threads:[~2021-05-25 15:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 15:25 [PATCH bpf-next v2] docs/bpf: add llvm_reloc.rst to explain llvm bpf relocations Yonghong Song
2021-05-25 15:31 ` Yonghong Song [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-25 3:33 Yonghong Song
2021-05-25 18:29 ` Fangrui Song
2021-05-25 18:52 ` Yonghong Song
2021-06-05 21:03 ` Fāng-ruì Sòng
2021-06-07 21:06 ` Yonghong Song
2021-06-07 22:08 ` Fāng-ruì Sòng
2021-06-08 4:22 ` Andrii Nakryiko
2021-06-08 4:32 ` Yonghong Song
2021-06-08 5:51 ` Fāng-ruì Sòng
2021-06-08 15:49 ` Alexei Starovoitov
2021-06-08 16:33 ` Fāng-ruì Sòng
2021-06-08 18:32 ` Alexei Starovoitov
2021-06-08 23:10 ` Fāng-ruì Sòng
2021-06-08 23:23 ` Alexei Starovoitov
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=4392b2d9-9643-00e9-c9fe-f722041adef8@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.