From: Jon Masters <jcm@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Stefan Assmann <sassmann@suse.de>, Len Brown <lenb@kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Olaf Dabrunz <od@suse.de>, 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>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent
Date: Mon, 12 Jan 2009 19:29:23 -0500 [thread overview]
Message-ID: <1231806563.4094.25.camel@perihelion.bos.jonmasters.org> (raw)
In-Reply-To: <m1d4esxfk2.fsf@frodo.ebiederm.org>
On Mon, 2009-01-12 at 15:36 -0800, Eric W. Biederman wrote:
> This hardware behavior is not specific to boot interrupts or Intel.
It's not specific to Intel, but it is a specific compatibility behavior.
> Is this case really so interesting and compelling that we want to fight
> through and figure what we need to do to make this work reliably on every
> x86 chipset?
How else do you propose implementing IRQ handling in e.g. the RT kernel?
We get a hardware interrupt, we can't FastEOI, we can't process
synchronously, we can't do all of those things you might expect.
Implementing RT requires that we delay handling of the IRQ until
arbitrarily later in the future when we get around to it.
Jon.
next prev parent reply other threads:[~2009-01-13 0:30 UTC|newest]
Thread overview: 30+ 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-12 11:09 ` Stefan Assmann
2009-01-12 11:37 ` Ingo Molnar
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-15 15:34 ` Olaf Dabrunz
2009-01-12 23:36 ` Eric W. Biederman
2009-01-13 0:29 ` Jon Masters [this message]
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 10:16 ` Stefan Assmann
2009-01-13 11:18 ` Stefan Assmann
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 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=1231806563.4094.25.camel@perihelion.bos.jonmasters.org \
--to=jcm@redhat.com \
--cc=bjorn.helgaas@hp.com \
--cc=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=od@suse.de \
--cc=rostedt@goodmis.org \
--cc=sassmann@suse.de \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).