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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Jul 2008 18:45:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Olaf Dabrunz <od@...e.de>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Jon Masters <jonathan@...masters.org>,
	Stefan Assmann <sassmann@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Ihno Krumreich <ihno@...e.de>,
	Sven Dietrich <sdietrich@...e.de>,
	Daniel Gollub <dgollub@...e.de>,
	Felix Foerster <ffoerster@...e.de>
Subject: Re: [PATCH 0/3] Boot IRQ quirks for Broadcom and AMD/ATI


* Jesse Barnes <jbarnes@...tuousgeek.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 ...

	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/