From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
Ken Chen <kenchen@google.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.28-rc4-mmotm1110 - you gotta be kidding me...
Date: Tue, 11 Nov 2008 15:58:44 +1100 [thread overview]
Message-ID: <20081111155844.7414bad8.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081110193713.d94ed39a.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
On Mon, 10 Nov 2008 19:37:13 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 10 Nov 2008 21:55:37 -0500 Valdis.Kletnieks@vt.edu wrote:
>
> > Somebody's been hitting the phunky pharmaceuticals in the last 4 days,
> > because this ball-of-joy snuck into linux-next.patch sometime between
> > -mmotm1106 and --mmotm1110.
> >
> > Seen in a 'make silentallconfig'
> >
> > Single-depth WCHAN output (SCHED_NO_NO_OMIT_FRAME_POINTER) [Y/n/?] (NEW) ?
> >
> > Calculate simpler /proc/<PID>/wchan values. If this option
> > is disabled then wchan values will recurse back to the
> > caller function. This provides more accurate wchan values,
> > at the expense of slightly more scheduling overhead.
>
> I got lost here.
>
> > If in doubt, say "Y".
> >
> > So if I say 'y', is that a request to disable it, or enable it? And
> > what exactly do I get if I vote *against* 'more accurate wchan values'?
> > Do I get everybody having the same wchan pointing somewhere in the
> > scheduler code, because that's where __builtin_return_address() points?
> >
> > And please - a triple negative in the Kconfig variable name? This has
> > gotta be a winner for poor taste in variable naming...
> >
>
> Even if that is all sorted out, how the heck is anyone to decide
> whether or not they need this thing?
>
> Also, if we really really are so wishy-washy indecisive that we need to
> make the function optional, it should if at all possible be made
> runtime-configurable, not compile-time.
This came from commit a87d091434ed2a34d647979ab12084139ee1fe41 ("x86,
sched: enable wchan config menu item on 64-bit"). We have had
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER for some time on various
architectures, this commit just made it available on x86_64 (by changing
its dependency from X86_32 to X86).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-11 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 2:55 Valdis.Kletnieks
2008-11-11 3:37 ` Andrew Morton
2008-11-11 4:58 ` Stephen Rothwell [this message]
2008-11-11 8:01 ` Ingo Molnar
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=20081111155844.7414bad8.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®