From: Len Brown <lenb@kernel.org>
To: Stefan Assmann <sassmann@suse.de>, Ingo Molnar <mingo@elte.hu>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Olaf Dabrunz <od@suse.de>,
Thomas
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent
Date: Fri, 09 Jan 2009 18:03:44 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0901091743310.20020@localhost.localdomain> (raw)
Stefan,
I had to exclude your changes to drivers/acpi/pci_irq.c from
e1d3a90846b40ad3160bf4b648d36c6badad39ac
in order to get some other changes to that file upstream in the
2.6.29 merge window.
I left the other parts of the quirk intact - so at the moment
on one of the quirked machines, you'll see
PCI quirk: reroute interrupts for...
but will not see
pci irq %d -> rerouted to legacy
as the quirk is effectively disabled.
I had difficulty trying to port this patch to the new pci_irq.c
because fundamentally I don't understand what it is trying
to do, and why.
The quirk is specific to Intel chipsets, so with all the
Linux guys now working at Intel, I'm hopeful that we can
reach a clear understanding of the issue and a consensus
on the proper fix.
BTW. I'm not excited about how the original patch
drops a chipset specific workaround inside the ACPI code
to go behind the mirrors and lie about what ACPI returns.
I'm hopeful that a better place for the workaround
can be found if this is the approach we need to take..
Can you help us understand what the failure is?
thanks,
-Len
next reply other threads:[~2009-01-09 23:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 23:03 Len Brown [this message]
2009-01-12 11:09 ` PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent 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
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=alpine.LFD.2.00.0901091743310.20020@localhost.localdomain \
--to=lenb@kernel.org \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=od@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox