mirror of
https://github.com/Fishwaldo/Star64_linux.git
synced 2025-06-20 13:41:30 +00:00
[ARM] fix naming of MODULE_START / MODULE_END
As of 73bdf0a60e
, the kernel needs
to know where modules are located in the virtual address space.
On ARM, we located this region between MODULE_START and MODULE_END.
Unfortunately, everyone else calls it MODULES_VADDR and MODULES_END.
Update ARM to use the same naming, so is_vmalloc_or_module_addr()
can work properly. Also update the comment on mm/vmalloc.c to
reflect that ARM also places modules in a separate region from the
vmalloc space.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
This commit is contained in:
parent
d2ed5cb80a
commit
ab4f2ee130
4 changed files with 13 additions and 13 deletions
|
@ -178,7 +178,7 @@ static int vmap_page_range(unsigned long addr, unsigned long end,
|
|||
static inline int is_vmalloc_or_module_addr(const void *x)
|
||||
{
|
||||
/*
|
||||
* x86-64 and sparc64 put modules in a special place,
|
||||
* ARM, x86-64 and sparc64 put modules in a special place,
|
||||
* and fall back on vmalloc() if that fails. Others
|
||||
* just put it in the vmalloc space.
|
||||
*/
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue