diff options
| author | KAMEZAWA Hiroyuki <[email protected]> | 2009-09-22 16:45:49 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2009-09-23 07:39:41 -0700 |
| commit | 26562c59fa9111ae3ea7b78045889662aac9e5ac (patch) | |
| tree | fe231752dcc4db5967bd798dbd9749a516678e18 /tools/perf/scripts/python | |
| parent | 3089aa1b0c07fb7c48f9829c619f50198307789d (diff) | |
kcore: register vmemmap range
Benjamin Herrenschmidt <[email protected]> pointed out that vmemmap
range is not included in KCORE_RAM, KCORE_VMALLOC ....
This adds KCORE_VMEMMAP if SPARSEMEM_VMEMMAP is used. By this, vmemmap
can be readable via /proc/kcore
Because it's not vmalloc area, vread/vwrite cannot be used. But the range
is static against the memory layout, this patch handles vmemmap area by
the same scheme with physical memory.
This patch assumes SPARSEMEM_VMEMMAP range is not in VMALLOC range. It's
correct now.
[[email protected]: fix typo]
Signed-off-by: KAMEZAWA Hiroyuki <[email protected]>
Cc: Jiri Slaby <[email protected]>
Cc: Ralf Baechle <[email protected]>
Cc: Benjamin Herrenschmidt <[email protected]>
Cc: WANG Cong <[email protected]>
Cc: Benjamin Herrenschmidt <[email protected]>
Cc: Randy Dunlap <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions