From: Steven Rostedt <rostedt@goodmis.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC PATCH kernel] trace: Make FTRACE_MCOUNT_USE_RECORDMCOUNT configurable
Date: Fri, 11 Feb 2022 21:47:22 -0500 [thread overview]
Message-ID: <20220211214722.4373ca83@rorschach.local.home> (raw)
In-Reply-To: <20220211014313.1790140-1-aik@ozlabs.ru>
On Fri, 11 Feb 2022 12:43:13 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> For whatever reason LLVM does not allow LTO (Link Time Optimization) if
> FTRACE_MCOUNT_USE_RECORDMCOUNT is enabled.
>
> This allows disabling just this option instead of disabling all FTRACE
> options.
What FTRACE options are you talking about?
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
>
> Or disabling FTRACE is the right thing to do if HAS_LTO_CLANG=y?
>
> Came from arch/Kconfig:
>
> config HAS_LTO_CLANG
> def_bool y
> depends on CC_IS_CLANG && LD_IS_LLD && AS_IS_LLVM
> depends on $(success,$(NM) --help | head -n 1 | grep -qi llvm)
> depends on $(success,$(AR) --help | head -n 1 | grep -qi llvm)
> depends on ARCH_SUPPORTS_LTO_CLANG
> depends on !FTRACE_MCOUNT_USE_RECORDMCOUNT <======
> depends on !KASAN || KASAN_HW_TAGS
> depends on !GCOV_KERNEL
>
>
> ---
> kernel/trace/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index a5eb5e7fd624..87d82d2b0b0b 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -704,7 +704,8 @@ config FTRACE_MCOUNT_USE_OBJTOOL
> depends on FTRACE_MCOUNT_RECORD
>
> config FTRACE_MCOUNT_USE_RECORDMCOUNT
> - def_bool y
> + bool "Enable FTRACE_MCOUNT_USE_RECORDMCOUNT"
> + default y
I don't think this does what you think it does.
This is not something that should be user selectable. What exactly are
you trying to accomplish here?
-- Steve
> depends on !FTRACE_MCOUNT_USE_PATCHABLE_FUNCTION_ENTRY
> depends on !FTRACE_MCOUNT_USE_CC
> depends on !FTRACE_MCOUNT_USE_OBJTOOL
next prev parent reply other threads:[~2022-02-12 2:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 1:43 [RFC PATCH kernel] trace: Make FTRACE_MCOUNT_USE_RECORDMCOUNT configurable Alexey Kardashevskiy
2022-02-12 0:10 ` Nick Desaulniers
2022-02-14 16:10 ` Sami Tolvanen
2022-02-16 4:51 ` Alexey Kardashevskiy
2022-02-16 9:51 ` Naveen N. Rao
2022-02-12 2:47 ` Steven Rostedt [this message]
2022-02-16 1:19 ` Alexey Kardashevskiy
2022-02-16 1:46 ` Steven Rostedt
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=20220211214722.4373ca83@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=aik@ozlabs.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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