diff options
author | Pavel Tatashin <[email protected]> | 2017-05-31 11:25:20 -0400 |
---|---|---|
committer | David S. Miller <[email protected]> | 2017-06-06 13:45:28 -0700 |
commit | 588974857359861891f478a070b1dc7ae04a3880 (patch) | |
tree | 179dd8a5d88a0b14a199891aff7f562ad71fc317 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | f322980b74a15e08f8c70a34a5864ecdbf957251 (diff) |
sparc64: reset mm cpumask after wrap
After a wrap (getting a new context version) a process must get a new
context id, which means that we would need to flush the context id from
the TLB before running for the first time with this ID on every CPU. But,
we use mm_cpumask to determine if this process has been running on this CPU
before, and this mask is not reset after a wrap. So, there are two possible
fixes for this issue:
1. Clear mm cpumask whenever mm gets a new context id
2. Unconditionally flush context every time process is running on a CPU
This patch implements the first solution
Signed-off-by: Pavel Tatashin <[email protected]>
Reviewed-by: Bob Picco <[email protected]>
Reviewed-by: Steven Sistare <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions