Searched hist:d7917ba7051e3fd12ebe2d5a09b29fb3a2b38190 (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/powerpc/mm/ |
| H A D | mmu_decl.h | diff d7917ba7051e3fd12ebe2d5a09b29fb3a2b38190 Tue Apr 15 14:52:22 CDT 2008 Kumar Gala <galak@kernel.crashing.org> [POWERPC] Introduce lowmem_end_addr to distinguish from total_lowmem
total_lowmem represents the amount of low memory, not the physical
address that low memory ends at. If the start of memory is at 0 it
happens that total_lowmem can be used as both the size and the address
that lowmem ends at (or more specifically one byte beyond the end).
To make the code a bit more clear and deal with the case when the start of
memory isn't at physical 0, we introduce lowmem_end_addr that represents
one byte beyond the last physical address in the lowmem region.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
|
| H A D | init_32.c | diff d7917ba7051e3fd12ebe2d5a09b29fb3a2b38190 Tue Apr 15 14:52:22 CDT 2008 Kumar Gala <galak@kernel.crashing.org> [POWERPC] Introduce lowmem_end_addr to distinguish from total_lowmem
total_lowmem represents the amount of low memory, not the physical
address that low memory ends at. If the start of memory is at 0 it
happens that total_lowmem can be used as both the size and the address
that lowmem ends at (or more specifically one byte beyond the end).
To make the code a bit more clear and deal with the case when the start of
memory isn't at physical 0, we introduce lowmem_end_addr that represents
one byte beyond the last physical address in the lowmem region.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
|
| H A D | init_64.c | diff d7917ba7051e3fd12ebe2d5a09b29fb3a2b38190 Tue Apr 15 14:52:22 CDT 2008 Kumar Gala <galak@kernel.crashing.org> [POWERPC] Introduce lowmem_end_addr to distinguish from total_lowmem
total_lowmem represents the amount of low memory, not the physical
address that low memory ends at. If the start of memory is at 0 it
happens that total_lowmem can be used as both the size and the address
that lowmem ends at (or more specifically one byte beyond the end).
To make the code a bit more clear and deal with the case when the start of
memory isn't at physical 0, we introduce lowmem_end_addr that represents
one byte beyond the last physical address in the lowmem region.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
|
| H A D | mem.c | diff d7917ba7051e3fd12ebe2d5a09b29fb3a2b38190 Tue Apr 15 14:52:22 CDT 2008 Kumar Gala <galak@kernel.crashing.org> [POWERPC] Introduce lowmem_end_addr to distinguish from total_lowmem
total_lowmem represents the amount of low memory, not the physical
address that low memory ends at. If the start of memory is at 0 it
happens that total_lowmem can be used as both the size and the address
that lowmem ends at (or more specifically one byte beyond the end).
To make the code a bit more clear and deal with the case when the start of
memory isn't at physical 0, we introduce lowmem_end_addr that represents
one byte beyond the last physical address in the lowmem region.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
|