From: Hao Luo <haoluo@google.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
daniel@iogearbox.net, dwarves@vger.kernel.org, yhs@fb.com,
Hao Luo <haoluo@google.com>
Subject: [PATCH v2 0/2] pahole: Make encoding percpu vars into BTF optional.
Date: Mon, 21 Sep 2020 12:53:08 -0700 [thread overview]
Message-ID: <20200921195310.3070085-1-haoluo@google.com> (raw)
v1 -> v2:
- Use opt-out instead of opt-in. Rename the flag name to
'--skip_encoding_btf_vars'
Previous commit f3d9054ba8ff ("btf_encoder: Teach pahole to store
percpu variables in vmlinux BTF.") introduced a feature in btf_encoder
that encodes global symbols in BTF. However, this feature is not
protected by any flag. In order to avoid surprises after Pahole v1.18
rolls out, add a flag to toggle this feature off.
Also as a refactor, introduce '--btf_encode_force' to replace the
old '--force' and '-j' option that is used to forcefully emit BTF.
Hao Luo (2):
btf_encoder: Allow disabling BTF var encoding.
btf_encoder: Introduce option '--btf_encode_force'
btf_encoder.c | 5 ++++-
btf_encoder.h | 3 ++-
pahole.c | 22 +++++++++++++++++-----
3 files changed, 23 insertions(+), 7 deletions(-)
--
2.28.0.681.g6f77f65b4e-goog
next reply other threads:[~2020-09-21 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 19:53 Hao Luo [this message]
2020-09-21 19:53 ` [PATCH v2 1/2] btf_encoder: Allow disabling BTF var encoding Hao Luo
2020-09-21 19:53 ` [PATCH v2 2/2] btf_encoder: Introduce option '--btf_encode_force' Hao Luo
2020-09-21 19:56 ` [PATCH v2 0/2] pahole: Make encoding percpu vars into BTF optional Arnaldo Carvalho de Melo
2020-09-21 20:00 ` Hao Luo
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=20200921195310.3070085-1-haoluo@google.com \
--to=haoluo@google.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dwarves@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).