[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100402184501.GA4775@elte.hu>
Date: Fri, 2 Apr 2010 20:45:01 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: "Jan.Grossmann@...lnet.net" <Jan.Grossmann@...lnet.net>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
"Woodhouse, David" <david.woodhouse@...el.com>,
"Han, Weidong" <weidong.han@...el.com>,
"Song, Youquan" <youquan.song@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"x86@...nel.org" <x86@...nel.org>,
"stable@...nel.org" <stable@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: BUG: null pointer deref in dmar_ir_support
* Suresh Siddha <suresh.b.siddha@...el.com> wrote:
> On Fri, 2010-04-02 at 11:20 -0700, Ingo Molnar wrote:
> > * Suresh Siddha <suresh.b.siddha@...el.com> wrote:
> >
> > > @@ -1640,8 +1640,10 @@ int __init APIC_init_uniprocessor(void)
> > > }
> > > #endif
> > >
> > > +#ifndef CONFIG_SMP
> > > enable_IR_x2apic();
> > > default_setup_apic_routing();
> > > +#endif
> >
> > Instead of adding yet another ugly #ifdef please hide these details
> > properly, by making enable_IR_x2apic() and default_setup_apic_routing() a
> > NOP on !SMP.
>
> Ingo, These are not nops on !SMP. We should call these functions from
> APIC_init_uniprocessor() only if it is a UP kernel. For SMP kernel they are
> called from some where else.
Btw., that makes the cleanliness situation even worse ...
> With the current code, on SMP and with non SMP motherboard we were calling
> these routines twice which cause problem.
>
> I wanted to keep the patch simple for urgent/backport. I will clean this by
> restructuring the init code for 2.6.35
Ok, fair enough, i'll queue up this fix.
The best structure would be to integrate these init details into the APIC
driver methods and make UP-IOAPIC nothing particularly special.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists