linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Luczak <difrost.kernel@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: pgtable_32.h - prototype and section mismatch	fixes
Date: Mon, 14 Apr 2008 10:59:28 +0200	[thread overview]
Message-ID: <48031CF0.5060409@gmail.com> (raw)
In-Reply-To: <20080414085307.GG19865@elte.hu>

Ingo Molnar pisze:
> * Sam Ravnborg <sam@ravnborg.org> wrote:
> 
>>> hm, that's an interesting case: we need those annotations probably 
>>> because gcc decided to not inline those functions. (this is possible 
>>> via the new CONFIG_OPTIMIZE_INLINING=y option) Sam, what's your take 
>>> on that?
>> gcc uses different heuristics for inlining between the different 
>> versions. Therefore to achieve somehow predictable results I added 
>> -fno-inline-functions-called-once when CONFIG_DEBUG_SECTION_MISMATCH 
>> is enabled.
>>
>> So in the above case for any normal kernel build we would see that gcc 
>> inlined the above and everything is fine. But for the 
>> CONFIG_DEBUG_SECTION_MISMTCH cases we do not inline and thus we see 
>> that we have a section mismatch.
> 
> ah, ok. So i guess this will result in a few isolated cases of __init 
> annotations added to inline functions - Jacek fixed one such case - but 
> it should not result in the general spreading of __init annotations to 
> inline functions, correct? (which i was worried about)
> 

Yep, I was confused about that patch, thus I didn't sent it previously.

Hmm...I forgot that all my kernels where compiled with
CONFIG_OPTIMIZE_INLINING=y. There's no mismatch warning printed while
OPTIMIZE_INLINING is not set. Also I've made a fast look into objects and looks
like those two functions are really inlined. I will also take a look on those
functions with CONFIG_OPTIMIZE_INLINING=y && ONFIG_DEBUG_SECTION_MISMATCH=n.

-Jacek

      parent reply	other threads:[~2008-04-14  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 15:41 [PATCH] x86: pgtable_32.h - prototype and section mismatch fixes Jacek Luczak
2008-04-14  7:26 ` Ingo Molnar
2008-04-14  8:41   ` Sam Ravnborg
2008-04-14  8:53     ` Ingo Molnar
2008-04-14  8:59       ` Sam Ravnborg
2008-04-14  9:11         ` Jacek Luczak
2008-04-14  9:52           ` Sam Ravnborg
2008-04-14 11:21             ` Jacek Luczak
2008-04-14 18:31               ` Sam Ravnborg
2008-04-14  8:59       ` Jacek Luczak [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=48031CF0.5060409@gmail.com \
    --to=difrost.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).