All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Dabrunz <od@suse.de>
To: Stefan Assmann <sassmann@suse.de>, Jon Masters <jcm@redhat.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>, Len Brown <lenb@kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Jesse Barnes <jbarnes@>
Subject: Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent
Date: Thu, 15 Jan 2009 16:34:44 +0100	[thread overview]
Message-ID: <20090115153444.GT25512@suse.de> (raw)
In-Reply-To: <20090113182259.GN25512@suse.de>

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-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Olaf Dabrunz <od@suse.de>
To: Stefan Assmann <sassmann@suse.de>, Jon Masters <jcm@redhat.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>, Len Brown <lenb@kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Sven Dietrich <sdietrich@novell.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent
Date: Thu, 15 Jan 2009 16:34:44 +0100	[thread overview]
Message-ID: <20090115153444.GT25512@suse.de> (raw)
In-Reply-To: <20090113182259.GN25512@suse.de>

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


  reply	other threads:[~2009-01-15 15:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 23:03 PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent Len Brown
2009-01-09 23:03 ` Len Brown
2009-01-12 11:09 ` Stefan Assmann
2009-01-12 11:09   ` Stefan Assmann
2009-01-12 11:37   ` Ingo Molnar
2009-01-12 18:51   ` Bjorn Helgaas
2009-01-12 18:51     ` Bjorn Helgaas
2009-01-12 19:25     ` Jon Masters
2009-01-12 19:45       ` Bjorn Helgaas
2009-01-13 13:32       ` Stefan Assmann
2009-01-13 18:22         ` Olaf Dabrunz
2009-01-13 18:22           ` Olaf Dabrunz
2009-01-15 15:34           ` Olaf Dabrunz [this message]
2009-01-15 15:34             ` Olaf Dabrunz
2009-01-12 23:36     ` Eric W. Biederman
2009-01-13  0:29       ` Jon Masters
2009-01-13  1:47         ` Ingo Molnar
2009-01-13  3:47           ` Eric W. Biederman
2009-01-13  4:26             ` Jon Masters
2009-01-14 11:40               ` Ingo Molnar
2009-01-14 19:18                 ` Jon Masters
2009-01-14 22:42                   ` Eric W. Biederman
2009-01-14 22:53                     ` Steven Rostedt
2009-01-14 22:56                     ` Jon Masters
2009-01-15 12:36                       ` Olaf Dabrunz
2009-01-15 12:36                         ` Olaf Dabrunz
2009-01-15 10:16                     ` Stefan Assmann
2009-01-13 11:18     ` Stefan Assmann
2009-01-13 11:18       ` Stefan Assmann
2009-01-13 15:57       ` Olaf Dabrunz
2009-01-13 15:57         ` Olaf Dabrunz
2009-01-15  0:10         ` Bjorn Helgaas
2009-01-15 14:08           ` Stefan Assmann
2009-01-13  8:25   ` Shaohua Li
2009-01-14  9:57     ` Stefan Assmann
2009-01-14 15:48       ` Bjorn Helgaas
2009-01-14 15:55         ` Olaf Dabrunz
2009-01-14 15:55           ` Olaf Dabrunz
2009-01-14 16:52           ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090115153444.GT25512@suse.de \
    --to=od@suse.de \
    --cc=bjorn.helgaas@hp.com \
    --cc=jcm@redhat.com \
    --cc=lenb@kernel.org \
    --cc=mingo@elte.hu \
    --cc=sassmann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.