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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090115153444.GT25512@suse.de>
Date:	Thu, 15 Jan 2009 16:34:44 +0100
From:	Olaf Dabrunz <od@...e.de>
To:	Stefan Assmann <sassmann@...e.de>, Jon Masters <jcm@...hat.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	Len Brown <lenb@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	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 13-Jan-09, Olaf Dabrunz wrote:
> On 13-Jan-09, Stefan Assmann wrote:
> > Hi Jon,
> > 
> > Jon Masters wrote:
> > > 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.
> > 
> > Actually, most of the Boot Interrupt patches resulted from reading the
> > intel specs and observing the behavior of failing machines. We're trying
> > to wrap up all the information gathered in a paper, which is pretty time
> > consuming and a few steps away from being ready to publish.
> 
> We read the specs of the chips, analyzed code, put up hypotheses and
> tested them. Then read the specs again, finding new hypotheses and
> tested again. Also reading what you guys sent out to lkml and reading
> through the public discussions for *BSD, Darwin, XEN etc. helped.
> And some colleagues discussed hypotheses and solution attempts with us.
> 
> We summarized many of our end results in a presentation that we gave
> internally, and I am working on making this available online (in
> addition to the paper/slides that Stefan mentions below).

The presentation can be found at

    http://www.suse.de/~odabrunz/Boot_Interrupts_and_IRQ_Threads.pdf

Some parts of it have been corrected and updated.

Please do not miss the "Details" slides after the License and the
Disclaimer. The Details should answer many questions.

Thanks,

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

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