Searched hist:"73 bdf0a60e607f4b8ecc5aec597105976565a84f" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/arm/kernel/ |
| H A D | module.c | diff ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6 Thu Nov 06 11:11:07 CST 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] fix naming of MODULE_START / MODULE_END
As of 73bdf0a60e607f4b8ecc5aec597105976565a84f, 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>
|
| /openbmc/linux/arch/arm/include/asm/ |
| H A D | memory.h | diff ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6 Thu Nov 06 11:11:07 CST 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] fix naming of MODULE_START / MODULE_END
As of 73bdf0a60e607f4b8ecc5aec597105976565a84f, 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>
|
| /openbmc/linux/mm/ |
| H A D | vmalloc.c | diff ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6 Thu Nov 06 11:11:07 CST 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] fix naming of MODULE_START / MODULE_END
As of 73bdf0a60e607f4b8ecc5aec597105976565a84f, 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>
diff 73bdf0a60e607f4b8ecc5aec597105976565a84f Wed Oct 15 10:35:12 CDT 2008 Linus Torvalds <torvalds@linux-foundation.org> Introduce is_vmalloc_or_module_addr() and use with DEBUG_VIRTUAL
Impact: crash on module insertion with CONFIG_DEBUG_VIRTUAL
We would incorrectly BUG due to:
VIRTUAL_BUG_ON(!is_vmalloc_addr(vmalloc_addr) &&
!is_module_address(addr));
... because, at least on x86-64, is_module_address() doesn't do what
it should. This patch introduces is_vmalloc_or_module_addr(), which
is what we really want anyway, and uses it instead.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
| /openbmc/linux/arch/arm/mm/ |
| H A D | mmu.c | diff ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6 Thu Nov 06 11:11:07 CST 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] fix naming of MODULE_START / MODULE_END
As of 73bdf0a60e607f4b8ecc5aec597105976565a84f, 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>
|