summaryrefslogtreecommitdiffstats
path: root/Documentation/Changes
diff options
context:
space:
mode:
authorAniruddha Banerjee <aniruddhab@nvidia.com>2018-03-28 19:12:00 +0530
committerMarc Zyngier <marc.zyngier@arm.com>2018-03-29 11:47:50 +0100
commitaa08192a254d362a4d5317647a81de6996961aef (patch)
tree4078cc6883332ae0fda2dca708cd5ace43a4a354 /Documentation/Changes
parentd01d327406d9c36e066181240ac078b636871de8 (diff)
downloadblackbird-obmc-linux-aa08192a254d362a4d5317647a81de6996961aef.tar.gz
blackbird-obmc-linux-aa08192a254d362a4d5317647a81de6996961aef.zip
irqchip/gic: Take lock when updating irq type
Most MMIO GIC register accesses use a 1-hot bit scheme that avoids requiring any form of locking. This isn't true for the GICD_ICFGRn registers, which require a RMW sequence. Unfortunately, we seem to be missing a lock for these particular accesses, which could result in a race condition if changing the trigger type on any two interrupts within the same set of 16 interrupts (and thus controlled by the same CFGR register). Introduce a private lock in the GIC common comde for this particular case, making it cover both GIC implementations in one go. Cc: stable@vger.kernel.org Signed-off-by: Aniruddha Banerjee <aniruddhab@nvidia.com> [maz: updated changelog] Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'Documentation/Changes')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud