aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorMarc Zyngier <[email protected]>2015-03-27 14:15:02 +0000
committerJason Cooper <[email protected]>2015-03-29 19:25:45 +0000
commit263fcd312deffb9bf10f007f958dccfa64a807f5 (patch)
treec424529594bcb4798dc802860e67fbd0f6600d78 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent4559fbb3a9b1bde46afc739fa6c300826acdc19c (diff)
irqchip: gicv3-its: Fix encoding of collection's target redistributor
With a monolithic GICv3, redistributors are addressed using a linear number, while a distributed implementation uses physical addresses. When encoding a target address into a command, we strip the lower 16 bits, as redistributors are always 64kB aligned. This works perfectly well with a distributed implementation, but has the silly effect of always encoding target 0 in the monolithic case (unless you have more than 64k CPUs, of course). The obvious fix is to shift the linear target number by 16 when computing the target address, so that we don't loose any precious bit. Reported-by: Andre Przywara <[email protected]> Tested-by: Andre Przywara <[email protected]> Signed-off-by: Marc Zyngier <[email protected]> Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Jason Cooper <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions