summaryrefslogtreecommitdiff
path: root/mausezahn
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2015-11-09 15:40:47 +0100
committerTobias Klauser <tklauser@distanz.ch>2015-11-09 15:40:47 +0100
commitb2eaec6671ff7ff44bb2f93881ad30e6d6ba0d24 (patch)
tree0c4ddb694da06af1ded2fcd26acf29529c714477 /mausezahn
parent66e558ed51ff7d3d7bebb5f5d56114df5eb77e96 (diff)
csum: Remove unused parameter from calc_csum()
The `ccsum' parameter to calc_csum() is never used and is set to 0 by all callers. There's no reason to keep it, so remove it. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'mausezahn')
0 files changed, 0 insertions, 0 deletions
126b076aad062054c2637'>566cf877a1fcb6d6dc0126b076aad062054c2637 (diff)
irqdomain: Avoid activating interrupts more than once
Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are activated early"), we can end-up activating a PCI/MSI twice (once at allocation time, and once at startup time). This is normally of no consequences, except that there is some HW out there that may misbehave if activate is used more than once (the GICv3 ITS, for example, uses the activate callback to issue the MAPVI command, and the architecture spec says that "If there is an existing mapping for the EventID-DeviceID combination, behavior is UNPREDICTABLE"). While this could be worked around in each individual driver, it may make more sense to tackle the issue at the core level. In order to avoid getting in that situation, let's have a per-interrupt flag to remember if we have already activated that interrupt or not. Fixes: f3b0946d629c ("genirq/msi: Make sure PCI MSIs are activated early") Reported-and-tested-by: Andre Przywara <andre.przywara@arm.com> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/1484668848-24361-1-git-send-email-marc.zyngier@arm.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'tools/perf/bench/mem-memset-x86-64-asm.S')