From: Adrian Bunk <bunk@kernel.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: clear IO_APIC before enabing apic error vector. v2
Date: Mon, 31 Dec 2007 01:23:54 +0200 [thread overview]
Message-ID: <20071230232354.GA3083@does.not.exist> (raw)
In-Reply-To: <86802c440712301442q476979f0hef047a45e5444c84@mail.gmail.com>
On Sun, Dec 30, 2007 at 02:42:41PM -0800, Yinghai Lu wrote:
> On Dec 30, 2007 2:06 PM, Adrian Bunk <bunk@kernel.org> wrote:
> > On Sun, Dec 30, 2007 at 12:48:48PM -0800, Yinghai Lu wrote:
> > > On Dec 30, 2007 6:51 AM, Ingo Molnar <mingo@elte.hu> wrote:
> > > >
> > > > * Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
> > > >
> > > > > please check if you can replace the one in the x86-mm
> > > > >
> > > > > http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-x86.git;a=commitdiff;h=ffcbdc220a1520d006a837f33589c7c19ffbeb76
> > > > >
> > > > > the updated one avoid one link warning.
> > > >
> > > > please send delta patches instead - so that we can review the changes.
> > >
> > > will do that in another patch.
> > >
> > > >
> > > > > this is the updated verison that take enable_IO_APIC as extra call for
> > > > > setup_local_APIC to avoid linking warning.
> > > >
> > > > hm, what link warning did you get? Perhaps the following __cpuinit:
> > >
> > > WARNING: vmlinux.o(.text+0x163d5): Section mismatch: reference to
> > > .init.text:enable_IO_APIC (between 'setup_local_APIC' and
> > > 'apic_is_clustered_box')
> >
> > So you are doing complicated things for silencing the warning (there is
> > an easier ways for achieving it), but the real bug that you will get an
> > Oops when calling enable_IO_APIC() after bootup since it already got
> > freed stays?
>
> the enable_IO_APIC is actually doing clear_IO_APIC. and it is only
> called by BSP via setup_local_APIC
> and it is not called again after bootup
OK, this was a bit hidden inside your pointer games.
Please send a patch that ignores the warning (and therefore doesn't do
these pointer games), and I'll fix the warning in a followup patch.
> YH
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-12-30 23:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 3:52 [PATCH] x86_64: clear IO_APIC before enabing apic error vector. v2 Yinghai Lu
2007-12-30 14:51 ` Ingo Molnar
2007-12-30 20:48 ` Yinghai Lu
2007-12-30 22:06 ` Adrian Bunk
2007-12-30 22:42 ` Yinghai Lu
2007-12-30 23:23 ` Adrian Bunk [this message]
2007-12-31 0:01 ` Yinghai Lu
2007-12-31 0:28 ` Adrian Bunk
2007-12-31 0:56 ` Yinghai Lu
2008-01-01 23:17 ` Adrian Bunk
2007-12-31 1:03 ` Yinghai Lu
2008-01-01 23:18 ` Adrian Bunk
2007-12-30 21:30 ` [PATCH] x86_64: fix section warning about enable_IO_APIC and setup_local_APIC Yinghai Lu
2007-12-30 21:29 ` Ingo Molnar
2007-12-30 21:53 ` Yinghai Lu
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=20071230232354.GA3083@does.not.exist \
--to=bunk@kernel.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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