man: add mausezahn man-page - netsniff-ng.git - A high-performance Linux networking toolkit

diff options

author	Daniel Borkmann <dborkman@redhat.com>	2013-05-14 15:10:50 +0200
committer	Daniel Borkmann <dborkman@redhat.com>	2013-05-14 16:21:21 +0200
commit	c53e506238cc18c268027f1a9aa6d13c7c4a8506 (patch)
tree	94ec7355b736da3d3f6d530bc496a2f4375498e5 /trafgen
parent	b5db443e823fffb2afb818e27a07cb25b87803e6 (diff)

man: add mausezahn man-page

Add the mausezahn man-page that is modified on top of the original man-page by Herbert Haas. Signed-off-by: Daniel Borkmann <dborkman@redhat.com>

Diffstat (limited to 'trafgen')

0 files changed, 0 insertions, 0 deletions

fc4e8507936190e86a16ee8c&id2=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/util/cloexec.c')


context:
space:
mode: