From: Balbir Singh <bsingharora@gmail.com>
To: Christophe LEROY <christophe.leroy@c-s.fr>, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/configs: Enable function trace by default
Date: Thu, 13 Apr 2017 18:19:28 +1000 [thread overview]
Message-ID: <1492071568.8380.20.camel@gmail.com> (raw)
In-Reply-To: <eea3c818-f5ca-4cd9-c715-307104534970@c-s.fr>
On Thu, 2017-04-13 at 09:24 +0200, Christophe LEROY wrote:
> Hi Baldir
Hi Christophe, It's Balbir
>
> Le 13/04/2017 à 09:03, Balbir Singh a écrit :
> > We expect to have these configs on by default, most
> > distros turn them off, its always good to have them on
> > so that we can use them and hopefully not break them
>
> Isn't it the purpose of the target allyesconfig to allow such tests ?
>
As a developer I don't use allyesconfig for submitting patches or testing
the kernel.
> FTRACE is quite CPU consumming, shouldn't it really be on by default ?
It does some work at boot to NOP out function entry points at _mcount
locations. Is that what you are referring to? Or the overhead of the
code in terms of size? Most distro kernels have tracing on by default.
The rest of the overhead is enablement based.
Thanks for the review!
Balbir Singh
next prev parent reply other threads:[~2017-04-13 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 7:03 [PATCH] powerpc/configs: Enable function trace by default Balbir Singh
2017-04-13 7:24 ` Christophe LEROY
2017-04-13 8:19 ` Balbir Singh [this message]
2017-04-13 8:41 ` Christophe LEROY
2017-04-13 11:51 ` Balbir Singh
2017-04-19 11:13 ` Anton Blanchard
2017-04-19 12:50 ` Balbir Singh
2017-04-19 13:46 ` Michael Ellerman
2017-04-13 15:21 ` Naveen N. Rao
2017-08-31 11:35 ` Michael Ellerman
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=1492071568.8380.20.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).