mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rakib Mullick <rakib.mullick@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Marcin Slusarz <marcin.slusarz@gmail.com>,
	mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: Fix false positive section mismatch  warnings in the apic code
Date: Mon, 20 Apr 2009 10:00:24 +0600	[thread overview]
Message-ID: <b9df5fa10904192100h6d5b728bldcc9337bb50d88b@mail.gmail.com> (raw)
In-Reply-To: <20090419111650.GA19873@uranus.ravnborg.org>

On 4/19/09, Sam Ravnborg <sam@ravnborg.org> wrote:
> If I understand it correct we have the following:

>  (data) struct apic apic_es7000.acpi_madt_oem_check =>
>  (function) es7000_acpi_madt_oem_check =>
>  (function) find_unisys_acpi_oem_table
>  (__init) early_acpi_os_unmap_memory
>
>  So the real fix is to:
>  1) annotate find_unisys_acpi_oem_table __init
>  2) annotate es7000_acpi_madt_oem_check __init
>  3) teach modpost that struct apic apic_es7000 may reference __init
>
>  Step 3 is done using __refdata
>
>  Based on the above analysis I would assume the best fix
>  would look like this the following.
>  [I only looked at the first warning]
>
>  Rabik/Marcin - if you agree in the analysis could you produce
>  a proper patch and send to Ingo - thanks.
>
>  You can add my:
>  Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
>  if the patch is ok.
>
>         Sam
Hi Sam, after applying your suggested three steps, we still have the
following warning:

WARNING: arch/x86/kernel/built-in.o(.text+0x36174): Section mismatch
in reference from the function unmap_unisys_acpi_oem_table() to the
function .init.text:__acpi_unmap_table()
The function unmap_unisys_acpi_oem_table() references
the function __init __acpi_unmap_table().
This is often because unmap_unisys_acpi_oem_table lacks a __init
annotation or the annotation of __acpi_unmap_table is wrong.

So, I think we've to annote unmap_unisys_acpi_oem_table with __init (
If we apply Sam's suggested steps). If anything else please notice.

Rakib.

  reply	other threads:[~2009-04-20  4:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  2:41 [PATCH] x86: Fix section mismatches in apic Rakib Mullick
2009-04-19  9:30 ` [tip:x86/urgent] x86: Fix false positive section mismatch warnings in the apic code tip-bot for Rakib Mullick
2009-04-19  9:47   ` Marcin Slusarz
2009-04-19  9:57     ` Ingo Molnar
2009-04-19 10:19       ` Marcin Slusarz
2009-04-19 13:56         ` Ingo Molnar
2009-04-19 11:16       ` Sam Ravnborg
2009-04-20  4:00         ` Rakib Mullick [this message]
2009-05-01 11:46           ` Sam Ravnborg
2009-05-09  9:35 [PATCH] x86: Fix false positive section mismatch in apic Rakib Mullick
2009-05-10  7:30 ` [tip:x86/urgent] x86: Fix false positive section mismatch warnings in the apic code tip-bot for Sam Ravnborg

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=b9df5fa10904192100h6d5b728bldcc9337bb50d88b@mail.gmail.com \
    --to=rakib.mullick@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    /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®