From: Brendan Higgins <brendanhiggins@google.com>
To: jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, akpm@linux-foundation.org,
changbin.du@intel.com, yamada.masahiro@socionext.com,
rdunlap@infradead.org, keescook@chromium.org,
andriy.shevchenko@linux.intel.com
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
davidgow@google.com, heidifahim@google.com,
Brendan Higgins <brendanhiggins@google.com>
Subject: [RFC v1 1/2] kbuild: add arch specific dependency for BTF support
Date: Mon, 27 Jan 2020 11:35:48 -0800 [thread overview]
Message-ID: <20200127193549.187419-2-brendanhiggins@google.com> (raw)
In-Reply-To: <20200127193549.187419-1-brendanhiggins@google.com>
Some archs (like UM) do not build with CONFIG_DEBUG_INFO_BTF=y, so add
an options for archs to select to opt-in or out of BTF typeinfo support.
Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
---
lib/Kconfig.debug | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index e4676b992eae9..f5bcb391f1b7d 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -238,9 +238,12 @@ config DEBUG_INFO_DWARF4
But it significantly improves the success of resolving
variables in gdb on optimized code.
+config ARCH_NO_BTF_TYPEINFO
+ bool
+
config DEBUG_INFO_BTF
bool "Generate BTF typeinfo"
- depends on DEBUG_INFO
+ depends on DEBUG_INFO && !ARCH_NO_BTF_TYPEINFO
help
Generate deduplicated BTF type information from DWARF debug info.
Turning this on expects presence of pahole tool, which will convert
--
2.25.0.341.g760bfbb309-goog
next prev parent reply other threads:[~2020-01-27 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 19:35 [RFC v1 0/2] arch: um: turn BTF_TYPEINFO support off Brendan Higgins
2020-01-27 19:35 ` Brendan Higgins [this message]
2020-01-28 3:27 ` [RFC v1 1/2] kbuild: add arch specific dependency for BTF support Masahiro Yamada
2020-01-28 7:25 ` Brendan Higgins
2020-01-27 19:35 ` [RFC v1 2/2] arch: um: turn BTF_TYPEINFO support off Brendan Higgins
2020-01-28 8:12 ` Anton Ivanov
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=20200127193549.187419-2-brendanhiggins@google.com \
--to=brendanhiggins@google.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=changbin.du@intel.com \
--cc=davidgow@google.com \
--cc=heidifahim@google.com \
--cc=jdike@addtoit.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=yamada.masahiro@socionext.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).