From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: dwarves@vger.kernel.org, bpf@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andriin@fb.com>, Yonghong Song <yhs@fb.com>,
Hao Luo <haoluo@google.com>, "Frank Ch. Eigler" <fche@redhat.com>,
Mark Wielaard <mjw@redhat.com>
Subject: [PATCH 3/3] btf_encoder: Include static functions to BTF data
Date: Mon, 26 Oct 2020 23:36:17 +0100 [thread overview]
Message-ID: <20201026223617.2868431-4-jolsa@kernel.org> (raw)
In-Reply-To: <20201026223617.2868431-1-jolsa@kernel.org>
Removing the condition to skip static functions.
Getting extra 23k functions on my kernel .config:
nr .BTF size (bytes)
before: 23291 3342279
after: 46606 4361045
The BTF section size increased of about 1MB.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
---
btf_encoder.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/btf_encoder.c b/btf_encoder.c
index 99b9abe36993..03a4bef11947 100644
--- a/btf_encoder.c
+++ b/btf_encoder.c
@@ -485,9 +485,6 @@ int cu__encode_btf(struct cu *cu, int verbose, bool force,
int btf_fnproto_id, btf_fn_id;
const char *name;
- if (!fn->external)
- continue;
-
/*
* We need to generate just single BTF instance for the
* function, while DWARF data contains multiple instances
--
2.26.2
next prev parent reply other threads:[~2020-10-26 22:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 22:36 [RFC 0/3] pahole: Workaround dwarf bug for function encoding Jiri Olsa
2020-10-26 22:36 ` [PATCH 1/3] btf_encoder: Move find_all_percpu_vars in generic config function Jiri Olsa
2020-10-27 23:12 ` Andrii Nakryiko
2020-10-27 23:54 ` Hao Luo
2020-10-28 15:51 ` Jiri Olsa
2020-10-26 22:36 ` [PATCH 2/3] btf_encoder: Change functions check due to broken dwarf Jiri Olsa
2020-10-27 23:20 ` Andrii Nakryiko
2020-10-28 15:50 ` Jiri Olsa
2020-10-26 22:36 ` Jiri Olsa [this message]
2020-10-27 23:21 ` [PATCH 3/3] btf_encoder: Include static functions to BTF data Andrii Nakryiko
2020-10-28 15:53 ` Jiri Olsa
2020-10-27 23:13 ` [RFC 0/3] pahole: Workaround dwarf bug for function encoding Andrii Nakryiko
2020-10-28 15:49 ` Jiri Olsa
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=20201026223617.2868431-4-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=acme@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=fche@redhat.com \
--cc=haoluo@google.com \
--cc=mjw@redhat.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