From: Yonghong Song <yhs@meta.com>
To: Eduard Zingerman <eddyz87@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, kernel-team@fb.com,
yhs@fb.com, arnaldo.melo@gmail.com
Subject: Re: [RFC bpf-next 09/12] kbuild: Header guards for types from include/uapi/*.h in kernel BTF
Date: Thu, 27 Oct 2022 15:44:04 -0700 [thread overview]
Message-ID: <7a3ebc5f-b07f-0336-abb1-627f7a73b2cb@meta.com> (raw)
In-Reply-To: <6e57811b-229a-e4f8-ca7e-fe826cde4be4@meta.com>
On 10/27/22 11:55 AM, Yonghong Song wrote:
>
>
> On 10/27/22 11:43 AM, Yonghong Song wrote:
>>
>>
>> On 10/25/22 3:27 PM, Eduard Zingerman wrote:
>>> Use pahole --header_guards_db flag to enable encoding of header guard
>>> information in kernel BTF. The actual correspondence between header
>>> file and guard string is computed by the scripts/infer_header_guards.pl.
>>>
>>> The encoded header guard information could be used to restore the
>>> original guards in the vmlinux.h, e.g.:
>>>
>>> include/uapi/linux/tcp.h:
>>>
>>> #ifndef _UAPI_LINUX_TCP_H
>>> #define _UAPI_LINUX_TCP_H
>>> ...
>>> union tcp_word_hdr {
>>> struct tcphdr hdr;
>>> __be32 words[5];
>>> };
>>> ...
>>> #endif /* _UAPI_LINUX_TCP_H */
>>>
>>> vmlinux.h:
>>>
>>> ...
>>> #ifndef _UAPI_LINUX_TCP_H
>>>
>>> union tcp_word_hdr {
>>> struct tcphdr hdr;
>>> __be32 words[5];
>>> };
>>>
>>> #endif /* _UAPI_LINUX_TCP_H */
>>> ...
>>>
>>> Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
>>> ---
>>> scripts/link-vmlinux.sh | 13 ++++++++++++-
>>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
>>> index 918470d768e9..f57f621eda1f 100755
>>> --- a/scripts/link-vmlinux.sh
>>> +++ b/scripts/link-vmlinux.sh
>>> @@ -110,6 +110,7 @@ vmlinux_link()
>>> gen_btf()
>>> {
>>> local pahole_ver
>>> + local extra_flags
>>> if ! [ -x "$(command -v ${PAHOLE})" ]; then
>>> echo >&2 "BTF: ${1}: pahole (${PAHOLE}) is not available"
>>> @@ -122,10 +123,20 @@ gen_btf()
>>> return 1
>>> fi
>>> + if [ "${pahole_ver}" -ge "124" ]; then
>>> + scripts/infer_header_guards.pl \
>>
>> We should have full path like
>> ${srctree}/scripts/infer_header_guards.pl
>> so it can work if build directory is different from source directory.
>
> handling arguments for infer_header_guards.pl should also take
> care of full file path.
>
> + /home/yhs/work/bpf-next/scripts/infer_header_guards.pl include/uapi
> include/generated/uapi arch/x86/include/uapi
> arch/x86/include/generated/uapi
> + return 1
Also, please pay attention to bpf selftest result. I see quite a
few selftest failures with this patch set.
>>
>>> + include/uapi \
>>> + include/generated/uapi \
>>> + arch/${SRCARCH}/include/uapi \
>>> + arch/${SRCARCH}/include/generated/uapi \
>>> + > .btf.uapi_header_guards || return 1;
>>> + extra_flags="--header_guards_db .btf.uapi_header_guards"
>>> + fi
>>> +
>>> vmlinux_link ${1}
>>> info "BTF" ${2}
>>> - LLVM_OBJCOPY="${OBJCOPY}" ${PAHOLE} -J ${PAHOLE_FLAGS} ${1}
>>> + LLVM_OBJCOPY="${OBJCOPY}" ${PAHOLE} -J ${PAHOLE_FLAGS}
>>> ${extra_flags} ${1}
>>> # Create ${2} which contains just .BTF section but no symbols. Add
>>> # SHF_ALLOC because .BTF will be part of the vmlinux image.
>>> --strip-all
next prev parent reply other threads:[~2022-10-27 22:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 22:27 [RFC bpf-next 00/12] Use uapi kernel headers with vmlinux.h Eduard Zingerman
2022-10-25 22:27 ` [RFC bpf-next 01/12] libbpf: Deduplicate unambigous standalone forward declarations Eduard Zingerman
2022-10-27 22:07 ` Andrii Nakryiko
2022-10-31 1:00 ` Eduard Zingerman
2022-10-31 15:49 ` Eduard Zingerman
2022-11-01 17:08 ` Alan Maguire
2022-11-01 17:37 ` Eduard Zingerman
2022-10-25 22:27 ` [RFC bpf-next 02/12] selftests/bpf: Tests for standalone forward BTF declarations deduplication Eduard Zingerman
2022-10-25 22:27 ` [RFC bpf-next 03/12] libbpf: Support for BTF_DECL_TAG dump in C format Eduard Zingerman
2022-10-27 22:36 ` Andrii Nakryiko
2022-10-25 22:27 ` [RFC bpf-next 04/12] selftests/bpf: Tests " Eduard Zingerman
2022-10-25 22:27 ` [RFC bpf-next 05/12] libbpf: Header guards for selected data structures in vmlinux.h Eduard Zingerman
2022-10-27 22:44 ` Andrii Nakryiko
2022-10-25 22:27 ` [RFC bpf-next 06/12] selftests/bpf: Tests for header guards printing in BTF dump Eduard Zingerman
2022-10-25 22:27 ` [RFC bpf-next 07/12] bpftool: Enable header guards generation Eduard Zingerman
2022-10-25 22:27 ` [RFC bpf-next 08/12] kbuild: Script to infer header guard values for uapi headers Eduard Zingerman
2022-10-27 22:51 ` Andrii Nakryiko
2022-10-25 22:27 ` [RFC bpf-next 09/12] kbuild: Header guards for types from include/uapi/*.h in kernel BTF Eduard Zingerman
2022-10-27 18:43 ` Yonghong Song
2022-10-27 18:55 ` Yonghong Song
2022-10-27 22:44 ` Yonghong Song [this message]
2022-10-28 0:00 ` Eduard Zingerman
2022-10-28 0:14 ` Mykola Lysenko
2022-10-28 1:23 ` Yonghong Song
2022-10-28 1:21 ` Yonghong Song
2022-10-25 22:27 ` [RFC bpf-next 10/12] selftests/bpf: Script to verify uapi headers usage with vmlinux.h Eduard Zingerman
2022-10-25 22:28 ` [RFC bpf-next 11/12] selftests/bpf: Known good uapi headers for test_uapi_headers.py Eduard Zingerman
2022-10-25 22:28 ` [RFC bpf-next 12/12] selftests/bpf: script for infer_header_guards.pl testing Eduard Zingerman
2022-10-25 23:46 ` [RFC bpf-next 00/12] Use uapi kernel headers with vmlinux.h Alexei Starovoitov
2022-10-26 22:46 ` Eduard Zingerman
2022-10-26 11:10 ` Alan Maguire
2022-10-26 23:54 ` Eduard Zingerman
2022-10-27 23:14 ` Andrii Nakryiko
2022-10-28 1:33 ` Yonghong Song
2022-10-28 17:13 ` Andrii Nakryiko
2022-10-28 18:56 ` Yonghong Song
2022-10-28 21:35 ` Andrii Nakryiko
2022-11-01 16:01 ` Alan Maguire
2022-11-01 18:35 ` Alexei Starovoitov
2022-11-01 19:21 ` Eduard Zingerman
2022-11-01 19:44 ` Alexei Starovoitov
2022-11-11 21:55 ` Eduard Zingerman
2022-11-14 7:52 ` Yonghong Song
2022-11-14 21:13 ` Eduard Zingerman
2022-11-14 21:50 ` Alexei Starovoitov
2022-11-16 2:01 ` Eduard Zingerman
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=7a3ebc5f-b07f-0336-abb1-627f7a73b2cb@meta.com \
--to=yhs@meta.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=yhs@fb.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