From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, llvm@lists.linux.dev
Cc: Nathan Lynch <nathanl@linux.ibm.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicholas Piggin <npiggin@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Sathvika Vasireddy <sv@linux.ibm.com>,
Joel Stanley <joel@jms.id.au>,
linuxppc-dev@lists.ozlabs.org, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH kernel 2/3] powerpc/llvm: Sample config for LLVM LTO
Date: Fri, 11 Feb 2022 17:14:11 +0530 [thread overview]
Message-ID: <1644579444.bal9kji6uc.naveen@linux.ibm.com> (raw)
In-Reply-To: <20220211023125.1790960-3-aik@ozlabs.ru>
Alexey Kardashevskiy wrote:
>
> Disables CONFIG_FTRACE_MCOUNT_USE_RECORDMCOUNT as CONFIG_HAS_LTO_CLANG
> depends on it being disabled. In order to avoid disabling way too many
> options (like DYNAMIC_FTRACE/FUNCTION_TRACER), this converts
> FTRACE_MCOUNT_USE_RECORDMCOUNT from def_bool to bool.
<snip>
> +CONFIG_FTRACE_MCOUNT_USE_RECORDMCOUNT=n
I don't think that will work since we have no other ways of generating
mcount locations on powerpc. And since we decided to only support
DYNAMIC_FTRACE, I guess we will need to disable FUNCTION_TRACER to get
this working, for now.
I am looking into ways to get ftrace working in this scenario.
- Naveen
next prev parent reply other threads:[~2022-02-11 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 2:31 [PATCH kernel 0/3] powerpc/llvm/lto: Enable CONFIG_LTO_CLANG_THIN=y Alexey Kardashevskiy
2022-02-11 2:31 ` [PATCH kernel 1/3] powerpc/64: Allow LLVM LTO builds Alexey Kardashevskiy
2022-02-11 2:31 ` [PATCH kernel 2/3] powerpc/llvm: Sample config for LLVM LTO Alexey Kardashevskiy
2022-02-11 11:44 ` Naveen N. Rao [this message]
2022-02-12 0:05 ` Nick Desaulniers
2022-02-16 1:28 ` Alexey Kardashevskiy
2022-02-11 2:31 ` [PATCH kernel 3/3] powerpc/llvm/lto: Workaround conditional branches in FTR_SECTION_ELSE Alexey Kardashevskiy
2022-02-11 6:44 ` Russell Currey
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=1644579444.bal9kji6uc.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=dja@axtens.net \
--cc=farosas@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=nathanl@linux.ibm.com \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=sv@linux.ibm.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).