diff options
| author | Vasily Gorbik <gor@linux.ibm.com> | 2019-08-02 17:44:29 +0200 |
|---|---|---|
| committer | Vasily Gorbik <gor@linux.ibm.com> | 2019-08-06 13:58:34 +0200 |
| commit | 218ddd5acfeae9e19a2fa97c284bf3c2e9de8ebd (patch) | |
| tree | 066d640c9289dd5e91cb7858ce32511d9d681e38 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 8024b5a9fc2bed9a00f0bdba60b443fa3cc4bb5d (diff) | |
s390/setup: adjust start_code of init_mm to _text
After some investigation it doesn't look like init_mm fields
start_code/end_code are used anywhere besides potentially in dump_mm for
debugging purposes. Originally the value of 0 for start_code reflected
the presence of lowcore and early boot code. But with kaslr in place
start_code/end_code range should not span over unoccupied by the code
segment memory. So, adjust init_mm start_code to point at the beginning
of the code segment like other architectures do it.
Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions