diff options
| author | Baoquan He <[email protected]> | 2023-02-06 16:40:16 +0800 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2023-02-09 16:51:42 -0800 |
| commit | 06c8994626d1b7d8c26dfd06992d67703a274054 (patch) | |
| tree | 70659260d7b5ef9e4b37b076567e09a124d8bf65 /tools/perf/scripts/python | |
| parent | 869176a096068056b338b5cc1b0af93106007f5d (diff) | |
mm/vmalloc.c: allow vread() to read out vm_map_ram areas
Currently, vread can read out vmalloc areas which is associated with a
vm_struct. While this doesn't work for areas created by vm_map_ram()
interface because it doesn't have an associated vm_struct. Then in
vread(), these areas are all skipped.
Here, add a new function vmap_ram_vread() to read out vm_map_ram areas.
The area created with vmap_ram_vread() interface directly can be handled
like the other normal vmap areas with aligned_vread(). While areas which
will be further subdivided and managed with vmap_block need carefully read
out page-aligned small regions and zero fill holes.
Link: https://lkml.kernel.org/r/[email protected]
Reported-by: Stephen Brennan <[email protected]>
Signed-off-by: Baoquan He <[email protected]>
Reviewed-by: Lorenzo Stoakes <[email protected]>
Tested-by: Stephen Brennan <[email protected]>
Cc: Dan Carpenter <[email protected]>
Cc: Uladzislau Rezki (Sony) <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions