mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Artem Bityutskiy <dedekind1@gmail.com>, Michal Marek <mmarek@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: sections mismatch detection
Date: Wed, 6 Jan 2010 11:48:23 +0100	[thread overview]
Message-ID: <20100106104823.GA30439@merkur.ravnborg.org> (raw)
In-Reply-To: <1262772683.4263.147.camel@localhost>

On Wed, Jan 06, 2010 at 12:11:23PM +0200, Artem Bityutskiy wrote:
> Hi,
> 
> I wonder is it good time to enable DEBUG_SECTION_MISMATCH by default
> now? I mean, remove the following from lib/Kconfig.debug:
> 
> config DEBUG_SECTION_MISMATCH
>         bool "Enable full Section mismatch analysis"
>         depends on UNDEFINED
>         # This option is on purpose disabled for now.
>         # It will be enabled when we are down to a resonable number
>         # of section mismatch warnings (< 10 for an allyesconfig build)
> 
> Just spotted this, and decided to remind.

My original criteria for enabling this was that we had a warnign free build
for all*config on x86 and a few other architectures.
While focusing on this I never reached this goal as I usually ended
up with some problems related to CPU hotplug.
I dunno how close we are today at the "zero warning" target.

When people implemented CPU hotplug they started to use __cpuinit
not only for code used during init time but also for code used
solely for CPU hotplugging. That made it difficult to solve
all the corner cases.
Because __cpu* annotation was used outside the original scope
I suggested to remove them from the checks but alas got no response.
Running out of time I gave up.

But I can see a steady flow of section mismatch fixes so I think the
situation looks better these days.

As the kbuild maintainer traditionally has been a central person
in this respect (due to the functionality in modpost),
I would like Michal to support this if we decide to enable the option.

	Sam

  reply	other threads:[~2010-01-06 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 10:11 Artem Bityutskiy
2010-01-06 10:48 ` Sam Ravnborg [this message]
2010-01-06 11:38   ` Michal Marek
2010-01-06 12:04     ` Artem Bityutskiy
2010-01-07 23:03     ` Randy Dunlap
2010-01-08  5:42       ` Sam Ravnborg
2010-01-08 13:18         ` Michal Marek
2010-01-08 16:27           ` Sam Ravnborg
2010-01-08 16:32             ` Michal Marek

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=20100106104823.GA30439@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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®