diff options
author | Sinan Kaya <okaya@codeaurora.org> | 2016-06-29 04:27:35 -0400 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-07-02 01:38:34 +0200 |
commit | 4a6e68bf96c1fa293717d2f00a68a68c92fa4150 (patch) | |
tree | 56c64f7c97a006288ca0bbb40068c6c8ae8fa574 /drivers/rapidio | |
parent | 54794580f5949253520265e46c903878ab222d84 (diff) | |
download | linux-stable-4a6e68bf96c1fa293717d2f00a68a68c92fa4150.tar.gz linux-stable-4a6e68bf96c1fa293717d2f00a68a68c92fa4150.tar.bz2 linux-stable-4a6e68bf96c1fa293717d2f00a68a68c92fa4150.zip |
ACPI,PCI,IRQ: factor in PCI possible
The change introduced in commit 103544d86976 (ACPI,PCI,IRQ: reduce
resource requirements) omitted the initially applied PCI_POSSIBLE
penalty when the IRQ is active.
Incorrect calculation of the penalty leads the ACPI code to assigning
a wrong interrupt number to a PCI INTx interrupt.
This would not be as bad as it sounds in theory. It would just cause
the interrupts to be shared and result in performance penalty.
However, some drivers (like the parallel port driver) don't like
interrupt sharing and in the above case they will causes all of
the PCI drivers wanting to share the interrupt to be unable to
request it.
The issue has not been caught in testing because the behavior is
platform-specific and depends on the peripherals ending up sharing
the IRQ and their drivers.
Before the above commit the code would add the PCI_POSSIBLE value
divided by the number of possible IRQ users to the IRQ penalty
during initialization.
Later in that code path, if the IRQ is chosen as the active IRQ or
if it is used by ISA; additional penalties are added.
Fixes: 103544d86976 (ACPI,PCI,IRQ: reduce resource requirements)
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
Tested-by: Wim Osterholt <wim@djo.tudelft.nl>
[ rjw: Changelog ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/rapidio')
0 files changed, 0 insertions, 0 deletions