All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc3 (fixmap build error)
Date: Mon, 22 Nov 2010 08:20:10 -0800	[thread overview]
Message-ID: <4CEA983A.5000200@oracle.com> (raw)
In-Reply-To: <20101121214450.62fac5a4.akpm@linux-foundation.org>

On 11/21/10 21:44, Andrew Morton wrote:
> On Sun, 21 Nov 2010 20:33:07 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
>> On Sun, Nov 21, 2010 at 6:16 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>>
>>> I thought that I saw a patch for this one, but I can't find it now.
>>>
>>> on i386:
>>> arch/x86/built-in.o: In function `fix_to_virt':
>>> /usr/builds/linux-2.6.37-rc3/arch/x86/include/asm/fixmap.h:207: undefined reference to `__this_fixmap_does_not_exist'
>>
>> Hmm. Does it help to mark __set_fixmap_offset() as "__always_inline"
>> rather than just "inline"?
> 
> yup.

yep.  Acked-by: Randy Dunlap <randy.dunlap@oracle.com>


> 
> Subject: arch/x86/include/asm/fixmap.h: mark __set_fixmap_offset as __always_inline
> From: Andrew Morton <akpm@linux-foundation.org>
> 
> When compiling arch/x86/kernel/early_printk_mrst.c with i386 allmodconfig,
> gcc-4.1.0 generates an out-of-line copy of __set_fixmap_offset() which
> contains a reference to __this_fixmap_does_not_exist which the compiler cannot
> elide.
> 
> Marking __set_fixmap_offset() as __always_inline prevents this.
> 
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Feng Tang <feng.tang@intel.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  arch/x86/include/asm/fixmap.h |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff -puN arch/x86/kernel/early_printk_mrst.c~arch-x86-include-asm-fixmaph-mark-__set_fixmap_offset-as-__always_inline arch/x86/kernel/early_printk_mrst.c
> diff -puN arch/x86/include/asm/fixmap.h~arch-x86-include-asm-fixmaph-mark-__set_fixmap_offset-as-__always_inline arch/x86/include/asm/fixmap.h
> --- a/arch/x86/include/asm/fixmap.h~arch-x86-include-asm-fixmaph-mark-__set_fixmap_offset-as-__always_inline
> +++ a/arch/x86/include/asm/fixmap.h
> @@ -220,8 +220,8 @@ static inline unsigned long virt_to_fix(
>  }
>  
>  /* Return an pointer with offset calculated */
> -static inline unsigned long __set_fixmap_offset(enum fixed_addresses idx,
> -				phys_addr_t phys, pgprot_t flags)
> +static __always_inline unsigned long
> +__set_fixmap_offset(enum fixed_addresses idx, phys_addr_t phys, pgprot_t flags)
>  {
>  	__set_fixmap(idx, phys, flags);
>  	return fix_to_virt(idx) + (phys & (PAGE_SIZE - 1));
> _
> 


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-11-22 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 23:43 Linux 2.6.37-rc3 Linus Torvalds
2010-11-22  2:16 ` Linux 2.6.37-rc3 (fixmap build error) Randy Dunlap
2010-11-22  4:33   ` Linus Torvalds
2010-11-22  5:44     ` Andrew Morton
2010-11-22 16:20       ` Randy Dunlap [this message]
2010-11-24 10:12 ` Linux 2.6.37-rc3 Américo Wang

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=4CEA983A.5000200@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.