linux

iv/linux

History

Vineet Gupta 3dea30ca5b ARCv2: Elide sending new cross core intr if receiver didn't ack prev

ARConnect/MCIP IPI sending has a retry-wait loop in case caller had
not seen a previous such interrupt. Turns out that it is not needed at
all. Linux cross core calling allows coalescing multiple IPIs to same
receiver - it is fine as long as there is one.

This logic is built into upper layer already, at a higher level of
abstraction. ipi_send_msg_one() sets the actual msg payload, but it only
calls MCIP IPI sending if msg holder was empty (using
atomic-set-new-and-get-old construct). Thus it is unlikely that the
retry-wait looping was ever getting exercised at all.

Cc: Chuck Jordan <cjordan@synopsys.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>

2016-02-24 11:07:31 +05:30

boot

ARC: [plat-sim] unbork non default CONFIG_LINUX_LINK_BASE

2015-12-17 11:06:43 +05:30

configs

arc: get rid of DEVTMPFS dependency on INITRAMFS_SOURCE

2016-02-23 12:31:04 +05:30

include

ARCv2: SMP: Push IPI_IRQ into IPI provider

2016-02-24 11:07:31 +05:30

kernel

ARCv2: Elide sending new cross core intr if receiver didn't ack prev