summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorJames Hogan <james.hogan@imgtec.com>2015-09-15 22:19:04 +0100
committerJames Hogan <james.hogan@imgtec.com>2015-09-15 22:52:47 +0100
commit928df02bd46e2fe02cfd3127ba1814796d6d80b0 (patch)
tree7a5bcb900b44470941c6bad741522d5b606a3069 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f (diff)
metag: SMP: Fix 4KiB stack setup on secondary CPUs
Back in early 2008, 4KiB stack support was added to reduce memory consumption on workloads with lots of threads, using a separate IRQ stack per CPU to alleviate stack pressure. However the SMP code added a year and a half later didn't set up the IRQ stack when bringing up secondary CPUs, resulting in a crash when SMP is configured with 4KiB stacks, as soon as the first interrupt arrived on a secondary CPU. Fix with calls to irq_ctx_exit()/irq_ctx_exit() when bringing up/down a CPU. Signed-off-by: James Hogan <james.hogan@imgtec.com> Cc: linux-metag@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions