aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/mem-phys-addr.py
diff options
context:
space:
mode:
authorJulian Wiedmann <[email protected]>2020-03-06 09:13:10 +0100
committerDavid S. Miller <[email protected]>2020-03-09 18:16:06 -0700
commit13099824145a599c282dd9193d10577250f18382 (patch)
tree050671ae6858b088ca051c761d59bdd49363f663 /tools/perf/scripts/python/mem-phys-addr.py
parent3f95f55eb55daa17c047d731d1fb7854e5823478 (diff)
s390/qdio: add tighter controls for IRQ polling
Once the call to qdio_establish() has completed, qdio is free to deliver data IRQs to the device driver's IRQ poll handler. For qeth (the only qdio driver that currently uses IRQ polling) this is problematic, since the IRQs can arrive before its NAPI instance is even registered. Calling napi_schedule() from qeth_qdio_start_poll() then crashes in various nasty ways. Until recently qeth checked for IFF_UP to drop such early interrupts, but that's fragile as well since it doesn't enforce any ordering. Fix this properly by bringing up the qdio device in IRQS_DISABLED mode, and have the driver explicitly opt-in to receive data IRQs. qeth does so from qeth_open(), which kick-starts a NAPI poll and then calls qdio_start_irq() from qeth_poll(). Also add a matching qdio_stop_irq() in qeth_stop() to switch the qdio dataplane back into a disabled state. Fixes: 3d35dbe6224e ("s390/qeth: don't check for IFF_UP when scheduling napi") CC: Qian Cai <[email protected]> Reported-by: Qian Cai <[email protected]> Signed-off-by: Julian Wiedmann <[email protected]> Acked-by: Vasily Gorbik <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions