summaryrefslogtreecommitdiff
path: root/drivers/atm/suni.c
diff options
context:
space:
mode:
authorMarc Zyngier <marc.zyngier@arm.com>2016-12-20 18:23:22 +0300
committerMarc Zyngier <marc.zyngier@arm.com>2017-08-31 17:31:39 +0300
commit20b3d54ecba51c5fe476eea94ffdc463559c5c85 (patch)
tree2acd26be3bada3dc6b878ff1cdc7612fe4a750f4 /drivers/atm/suni.c
parent93f94ea0548c2628efe7d57e0989f06a14cedb53 (diff)
downloadlinux-20b3d54ecba51c5fe476eea94ffdc463559c5c85.tar.xz
irqchip/gic-v3-its: Add device proxy for VPE management if !DirectLpi
When we don't have the DirectLPI feature, we must work around the architecture shortcomings to be able to perform the required maintenance (interrupt masking, clearing and injection). For this, we create a fake device whose sole purpose is to provide a way to issue commands as if we were dealing with LPIs coming from that device (while they actually originate from the ITS). This fake device doesn't have LPIs allocated to it, but instead uses the VPE LPIs. Of course, this could be a real bottleneck, and a naive implementation would require 6 commands to issue an invalidation. Instead, let's allocate at least one event per physical CPU (rounded up to the next power of 2), and opportunistically map the VPE doorbell to an event. This doorbell will be mapped until we roll over and need to reallocate this slot. This ensures that most of the time, we only need 2 commands to issue an INV, INT or CLEAR, making the performance a lot better, given that we always issue a CLEAR on entry, and an INV on each side of a trapped WFI. Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'drivers/atm/suni.c')
0 files changed, 0 insertions, 0 deletions