|
|
|
[PATCH] ARM: Documentation: Add note about static mappings due latest VMALLOC changes | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Signed-off-by: Alexander Shiyan <shc_work@xxxxxxx> --- Documentation/arm/Porting | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/arm/Porting b/Documentation/arm/Porting index a492233..882d32f 100644 --- a/Documentation/arm/Porting +++ b/Documentation/arm/Porting @@ -91,8 +91,8 @@ DATAADDR VMALLOC_START VMALLOC_END - Virtual addresses bounding the vmalloc() area. There must not be - any static mappings in this area; vmalloc will overwrite them. + Virtual addresses bounding the vmalloc() area. Machine specific + static mappings are also located here through iotable_init(). The addresses must also be in the kernel segment (see above). Normally, the vmalloc() area starts VMALLOC_OFFSET bytes above the last virtual RAM address (found using variable high_memory). -- 1.7.3.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Site Home] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Linux FS] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]
|