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. > 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. At the moment I'm uploading the slides we showed at the 10th Real-Time Linux Workshop, which are a small, stripped down excerpt of our upcoming paper. It should be available soon at: ftp://ftp.suse.com/pub/people/sassmann/publication/boot_irq_quirks_rtlws10.pdf Meanwhile I'd suggest to have a look at United States Patent 6466998. That is intels patent for this interrupt routing mechanism. Hope this is helpful, we'll try to make more information available asap. > > Jon. > Stefan -- Stefan Assmann | SUSE LINUX Products GmbH Software Engineer | Maxfeldstr. 5, D-90409 Nuernberg Mail: sassmann@xxxxxxx | GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
