linux-kernel - Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent

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]

Message-Id: <1231788349.4094.21.camel@perihelion.bos.jonmasters.org>
Date:	Mon, 12 Jan 2009 14:25:49 -0500
From:	Jon Masters <jcm@...hat.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Stefan Assmann <sassmann@...e.de>, Len Brown <lenb@...nel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Olaf Dabrunz <od@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org, Sven Dietrich <sdietrich@...ell.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>
Subject: Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot
	interrupt equivalent

On Mon, 2009-01-12 at 11:51 -0700, Bjorn Helgaas wrote:
> (I added Eric, Maciej, and Jon because they participated in
> previous discussion here: http://lkml.org/lkml/2008/6/2/269)

Thanks. You know what I'd really like even more than being on the CC?
I'd *love* someone to post a link to documentation on how this actually
is supposed to work. We had to guess last time because none of the
public documentation actually explains this. The guys at SuSE likely
received some docs, but I'm not sure where from or the title thereof.

If we all knew how this was supposed to work then we might have a much
better likelihood of fixing this behavior. It's only going to get worse
over time - we want to get threaded IRQs upstream (I'm about to be
poking at that again over here) and that'll mean mainline has to learn
to deal with these boot interrupts just as much as RT does today.

Jon.

--
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/