diff options
| author | Balasubramani Vivekanandan <[email protected]> | 2015-04-14 15:48:18 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2015-04-14 16:49:05 -0700 |
| commit | 2415b9f5cb048a803b30b790af994ba71ff0bd4c (patch) | |
| tree | 616a11b2a493045bee0c5e963ccdfc00c9d64d7c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 2a8e70026435ad97570a1e0a0c4c941e0f700a3e (diff) | |
memcg: print cgroup information when system panics due to panic_on_oom
If kernel panics due to oom, caused by a cgroup reaching its limit, when
'compulsory panic_on_oom' is enabled, then we will only see that the OOM
happened because of "compulsory panic_on_oom is enabled" but this doesn't
tell the difference between mempolicy and memcg. And dumping system wide
information is plain wrong and more confusing. This patch provides the
information of the cgroup whose limit triggerred panic
Signed-off-by: Balasubramani Vivekanandan <[email protected]>
Acked-by: Michal Hocko <[email protected]>
Cc: Johannes Weiner <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions