From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>,
linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH v2 typo-fixed] initcall: add config option for compiling initcall_debug
Date: Thu, 31 Mar 2011 00:31:06 +0200 [thread overview]
Message-ID: <201103310031.06374.rjw@sisk.pl> (raw)
In-Reply-To: <20110329155751.e7ba346a.akpm@linux-foundation.org>
On Wednesday, March 30, 2011, Andrew Morton wrote:
> On Mon, 28 Mar 2011 11:51:31 +0400
> Konstantin Khlebnikov <khlebnikov@openvz.org> wrote:
>
> > This patch adds bool config option CONFIG_INITCALL_DEBUG for
> > compiling initcalls debuging, it on by default to keep current behaviour.
> >
> > With CONFIG_INITCALL_DEBUG=n bloat-o-meter shows:
> >
> > add/remove: 0/7 grow/shrink: 3/10 up/down: 88/-1448 (-1360)
> > function old new delta
> > device_resume 350 404 +54
> > __device_suspend 331 363 +32
> > device_resume_noirq 230 232 +2
> > kernel_init 355 354 -1
> > initcall_debug 4 - -4
> > __param_str_initcall_debug 15 - -15
> > dpm_suspend 431 415 -16
> > syscore_suspend 280 250 -30
> > syscore_shutdown 123 93 -30
> > __param_initcall_debug 32 - -32
> > syscore_resume 215 173 -42
> > static.initcall_debug_start 71 - -71
> > static.initcall_debug_report 102 - -102
> > legacy_resume 129 - -129
> > async_synchronize_cookie_domain 286 152 -134
> > legacy_suspend 135 - -135
> > async_run_entry_fn 348 188 -160
> > do_one_initcall 364 197 -167
> > pm_op 536 366 -170
> > pm_noirq_op 576 366 -210
>
> Well. One hopes that most things which use initcall_debug are
> marked __init or __initdata.
>
> I see that async and pm have borrowed inticall_debug for reasonably
> appropriate reasons, but I wonder if all that is permanent code, or if
> it will later get removed. Because if it gets removed, this patch
> becomes rather pointless.
This is permanent code, as far as PM is concerned.
Thanks,
Rafael
prev parent reply other threads:[~2011-03-30 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 11:55 [PATCH] initcall: add config option for compiling initcall_debug Konstantin Khlebnikov
2011-03-27 17:43 ` Randy Dunlap
2011-03-28 7:53 ` Konstantin Khlebnikov
2011-03-28 7:51 ` [PATCH v2 typo-fixed] " Konstantin Khlebnikov
2011-03-29 22:57 ` Andrew Morton
2011-03-30 22:31 ` Rafael J. Wysocki [this message]
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=201103310031.06374.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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