Re: [PATCH 0/3] Boot IRQ quirks for Broadcom and AMD/ATI

[Olaf Dabrunz <od@suse.de>]

On 14-Jul-08, Olaf Dabrunz wrote:
> On 14-Jul-08, Ingo Molnar wrote:
> > 
> > * Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > 
> > > > applied to tip/x86/pci-ioapic-boot-irq-quirks, thanks Olaf.
> > > >
> > > > Jesse, what do you think about this topic? We are keeping it 
> > > > separate for the time being. They are not particularly pretty, but 
> > > > being able to mask/unmask irqs (without generating those legacy IRQs 
> > > > and creating an IRQ storm) is essential to -rt.
> > > 
> > > See my other reply; the branch looks good.  I agree that making sure 
> > > -rt can work is an important feature.  My only concern is that this is 
> > > touching so much hardware specific code that *something* is likely to 
> > > break.  But as long as Olaf & co. can help track down any issues, I'm 
> > > ok with it.
> > 
> > ok. We'll cook it a bit more in tip/master and then send it over to you 
> > once all the dependent changes have gone upstream in the merge window, 
> > ok? I think it's v2.6.27 worthy stuff - nicely localized, sufficiently 
> > finegrained and any problems with it has to be debugged the hard way by 
> > exposing people to them ...
> 
> Ack. :)

I am working on a consolidated patch set for AKMP. It integrates all
fixes and adds a config option CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS
(prepared by Stefan Assmann), which can default to off for vanilla and to
on for RT / threaded IRQ handling. This means that the whole patchset
can (in principle) be applied to vanilla and RT without change. Also
CONFIG_PREEMPT_HARDIRQ can "select CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS".

If you don't mind, I will send the full set out today.

-- 
Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg