From: "H. Peter Anvin" <hpa@zytor.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Witold Baryluk <baryluk@smp.if.uj.edu.pl>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Subject: Re: WARNING: arch/x86/built-in.o: Section mismatch in reference from the variable test_nmi_ipi_callback_na to function .ini.text:test_nmi_ipi_callback
Date: Mon, 04 Jun 2012 07:59:41 -0700 [thread overview]
Message-ID: <4FCCCD5D.6010005@zytor.com> (raw)
In-Reply-To: <20120604143643.GJ32472@redhat.com>
On 06/04/2012 07:36 AM, Don Zickus wrote:
>
> Basically the test registers two nmi_handlers, run some tests, and
> then unregisters them. Those handlers are what the compiler seems to be
> complaining about. I do not know what magic to pass the compiler to let
> it know that both of the handlers will be unregistered before the init
> section is destroyed.
>
> Perhaps I should tag those callbacks with __ref? I am not sure the right
> thing to do here.
>
Using __ref is the right thing, although __ref is hard to use right...
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-06-04 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 16:15 WARNING: arch/x86/built-in.o: Section mismatch in reference from the variable test_nmi_ipi_callback_na to function .ini.text:test_nmi_ipi_callback Witold Baryluk
2012-06-04 14:36 ` Don Zickus
2012-06-04 14:59 ` H. Peter Anvin [this message]
2012-06-04 15:08 ` Don Zickus
2012-06-04 16:35 ` Sam Ravnborg
2012-06-04 19:08 ` Different WARNING: drivers/scsi/fcoe/libfcoe.o(.init.text+0x1a): Section mismatch in reference from the function init_module() to the function .exit.text:fcoe_transport_exit() Witold Baryluk
2012-06-04 19:17 ` Sam Ravnborg
2012-06-04 20:52 ` Zou, Yi
2012-06-04 22:33 ` Sam Ravnborg
2012-06-04 23:11 ` Zou, Yi
2012-06-06 18:59 ` [PATCH] libfcoe: Fix section mismatch Robert Love
2012-06-06 19:58 ` 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=4FCCCD5D.6010005@zytor.com \
--to=hpa@zytor.com \
--cc=baryluk@smp.if.uj.edu.pl \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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