From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Konstantin Khlebnikov <k.khlebnikov@samsung.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andrey Ryabinin <a.ryabinin@samsung.com>
Subject: Re: [PATCH RFC] ARM: option for loading modules into vmalloc area
Date: Tue, 18 Nov 2014 17:34:13 +0000 [thread overview]
Message-ID: <20141118173413.GB4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20141118172146.3784.81151.stgit@buzz>
On Tue, Nov 18, 2014 at 08:21:46PM +0400, Konstantin Khlebnikov wrote:
> Usually modules are loaded into small area prior to the kernel
> text because they are linked with the kernel using short calls.
> Compile-time instrumentation like GCOV or KASAN bloats code a lot,
> and as a result huge modules no longer fit into reserved area.
>
> This patch adds option CONFIG_MODULES_USE_VMALLOC which lifts
> limitation on amount of loaded modules. It links modules using
> long-calls (option -mlong-calls) and loads them into vmalloc area.
>
> In few places exported symbols are called from inline assembly.
> This patch adds macro for such call sites: __asmbl and __asmbl_clobber.
> Call turns into single 'bl' or sequence 'movw; movt; blx' depending on
> context and state of config option.
>
> Unfortunately this option isn't compatible with CONFIG_FUNCTION_TRACER.
> Compiler emits short calls to profiling function despite of -mlong-calls.
> This is a bug in GCC, but ftrace anyway needs an update to handle this.
It also isn't compatible with the older architectures which don't have
"blx".
> diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
> index 9d2cdda..9e0c4f4 100644
> --- a/arch/arm/mm/mmu.c
> +++ b/arch/arm/mm/mmu.c
> @@ -1161,16 +1161,15 @@ void __init sanity_check_meminfo(void)
>
> static inline void prepare_page_table(void)
> {
> - unsigned long addr;
> + unsigned long addr = 0;
> phys_addr_t end;
>
> /*
> * Clear out all the mappings below the kernel image.
> */
> - for (addr = 0; addr < MODULES_VADDR; addr += PMD_SIZE)
> - pmd_clear(pmd_off_k(addr));
> -
> #ifdef CONFIG_XIP_KERNEL
> + for ( ; addr < MODULES_VADDR; addr += PMD_SIZE)
> + pmd_clear(pmd_off_k(addr));
> /* The XIP kernel is mapped in the module area -- skip over it */
> addr = ((unsigned long)_etext + PMD_SIZE - 1) & PMD_MASK;
> #endif
This seems to be an unrelated change. In any case, it looks wrong to
me. Please describe what you are trying to achieve here.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-11-18 17:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 16:21 Konstantin Khlebnikov
2014-11-18 17:34 ` Russell King - ARM Linux [this message]
2014-11-18 18:13 ` Konstantin Khlebnikov
2014-11-19 13:40 ` Arnd Bergmann
2014-11-19 14:54 ` Ard Biesheuvel
2014-11-19 15:52 ` Konstantin Khlebnikov
2014-11-19 16:02 ` Ard Biesheuvel
2014-11-19 16:07 ` Russell King - ARM Linux
2014-11-19 16:25 ` Ard Biesheuvel
2014-11-19 16:32 ` Konstantin Khlebnikov
2014-11-19 16:38 ` Ard Biesheuvel
2014-11-19 16:55 ` Russell King - ARM Linux
2014-11-19 16:59 ` Nicolas Pitre
2014-11-19 16:41 ` Russell King - ARM Linux
2014-11-19 16:37 ` Nicolas Pitre
2014-11-19 16:41 ` Ard Biesheuvel
2014-11-19 16:49 ` Russell King - ARM Linux
2014-11-19 16:57 ` Nicolas Pitre
2014-11-19 16:59 ` Russell King - ARM Linux
2014-11-19 17:12 ` Nicolas Pitre
2014-11-19 17:59 ` Ard Biesheuvel
2014-11-19 18:22 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141118173413.GB4042@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=a.ryabinin@samsung.com \
--cc=k.khlebnikov@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®