-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[PATCH] ARM: cleanup vmalloc start/offset macros
VMALLOC_START and VMALLOC_OFFSET are common between all ARM machine classes. Move them into include/asm-arm/pgtable.h, but allow a machine class to override them if required. Signed-off-by: Russell King <rmk@arm.linux.org.uk>
- Loading branch information
Russell King
committed
May 3, 2005
1 parent
5cd0c34
commit 5c3073e
Showing
21 changed files
with
17 additions
and
209 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,4 @@ | ||
/* | ||
* linux/include/asm-arm/arch-cl7500/vmalloc.h | ||
*/ | ||
|
||
/* | ||
* Just any arbitrary offset to the start of the vmalloc VM area: the | ||
* current 8MB value just means that there will be a 8MB "hole" after the | ||
* physical memory until the kernel virtual memory starts. That means that | ||
* any out-of-bounds memory accesses will hopefully be caught. | ||
* The vmalloc() routines leaves a hole of 4kB between each vmalloced | ||
* area for the same reason. ;) | ||
*/ | ||
#define VMALLOC_OFFSET (8*1024*1024) | ||
#define VMALLOC_START (((unsigned long)high_memory + VMALLOC_OFFSET) & ~(VMALLOC_OFFSET-1)) | ||
#define VMALLOC_END (PAGE_OFFSET + 0x1c000000) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,5 @@ | ||
/* | ||
* linux/include/asm-arm/arch-ixp4xx/vmalloc.h | ||
*/ | ||
|
||
/* | ||
* Just any arbitrary offset to the start of the vmalloc VM area: the | ||
* current 8MB value just means that there will be a 8MB "hole" after the | ||
* physical memory until the kernel virtual memory starts. That means that | ||
* any out-of-bounds memory accesses will hopefully be caught. | ||
* The vmalloc() routines leaves a hole of 4kB between each vmalloced | ||
* area for the same reason. ;) | ||
*/ | ||
#define VMALLOC_OFFSET (8*1024*1024) | ||
#define VMALLOC_START (((unsigned long)high_memory + VMALLOC_OFFSET) & ~(VMALLOC_OFFSET-1)) | ||
#define VMALLOC_VMADDR(x) ((unsigned long)(x)) | ||
#define VMALLOC_END (0xFF000000) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,4 @@ | ||
/* | ||
* linux/include/asm-arm/arch-l7200/vmalloc.h | ||
*/ | ||
|
||
/* | ||
* Just any arbitrary offset to the start of the vmalloc VM area: the | ||
* current 8MB value just means that there will be a 8MB "hole" after the | ||
* physical memory until the kernel virtual memory starts. That means that | ||
* any out-of-bounds memory accesses will hopefully be caught. | ||
* The vmalloc() routines leaves a hole of 4kB between each vmalloced | ||
* area for the same reason. ;) | ||
*/ | ||
#define VMALLOC_OFFSET (8*1024*1024) | ||
#define VMALLOC_START (((unsigned long)high_memory + VMALLOC_OFFSET) & ~(VMALLOC_OFFSET-1)) | ||
#define VMALLOC_END (PAGE_OFFSET + 0x10000000) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,4 @@ | ||
/* | ||
* linux/include/asm-arm/arch-sa1100/vmalloc.h | ||
*/ | ||
|
||
/* | ||
* Just any arbitrary offset to the start of the vmalloc VM area: the | ||
* current 8MB value just means that there will be a 8MB "hole" after the | ||
* physical memory until the kernel virtual memory starts. That means that | ||
* any out-of-bounds memory accesses will hopefully be caught. | ||
* The vmalloc() routines leaves a hole of 4kB between each vmalloced | ||
* area for the same reason. ;) | ||
*/ | ||
#define VMALLOC_OFFSET (8*1024*1024) | ||
#define VMALLOC_START (((unsigned long)high_memory + VMALLOC_OFFSET) & ~(VMALLOC_OFFSET-1)) | ||
#define VMALLOC_END (0xe8000000) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,4 @@ | ||
/* | ||
* linux/include/asm-arm/arch-rpc/vmalloc.h | ||
*/ | ||
|
||
/* | ||
* Just any arbitrary offset to the start of the vmalloc VM area: the | ||
* current 8MB value just means that there will be a 8MB "hole" after the | ||
* physical memory until the kernel virtual memory starts. That means that | ||
* any out-of-bounds memory accesses will hopefully be caught. | ||
* The vmalloc() routines leaves a hole of 4kB between each vmalloced | ||
* area for the same reason. ;) | ||
*/ | ||
#define VMALLOC_OFFSET (8*1024*1024) | ||
#define VMALLOC_START (((unsigned long)high_memory + VMALLOC_OFFSET) & ~(VMALLOC_OFFSET-1)) | ||
#define VMALLOC_END (PAGE_OFFSET + 0x10000000) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters