| commit | 5fd9c6e214547a32d3da6ee4284c79004d667bc8 | |
| author | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Sat, 26 Jan 2008 13:11:00 +0000 (26 14:11 +0100) | ||
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | |
| Sat, 26 Jan 2008 13:11:12 +0000 (26 14:11 +0100) | ||
| tree | def2e218393c9867e9db939f1d379c005895a912 | treesnapshot (tar.gz zip) |
| parent | 8ffd74a0924e4e04f6455eb2d2187a9564678d01 | commitdiff |
[S390] Change vmalloc defintions
Currently the vmalloc area starts at a dynamic address depending on
the memory size. There was also an 8MB security hole after the
physical memory to catch out-of-bounds accesses.
We can simplify the code by putting the vmalloc area explicitely at
the top of the kernel mapping and setting the vmalloc size to a fixed
value of 128MB/128GB for 31bit/64bit systems. Part of the vmalloc
area will be used for the vmem_map. This leaves an area of 96MB/1GB
for normal vmalloc allocations.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Currently the vmalloc area starts at a dynamic address depending on
the memory size. There was also an 8MB security hole after the
physical memory to catch out-of-bounds accesses.
We can simplify the code by putting the vmalloc area explicitely at
the top of the kernel mapping and setting the vmalloc size to a fixed
value of 128MB/128GB for 31bit/64bit systems. Part of the vmalloc
area will be used for the vmem_map. This leaves an area of 96MB/1GB
for normal vmalloc allocations.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
| arch/s390/kernel/setup.c | diffblobblamehistory | |
| arch/s390/mm/vmem.c | diffblobblamehistory | |
| include/asm-s390/pgtable.h | diffblobblamehistory |