From: Ard Biesheuvel <ardb@kernel.org>
To: "chenjun (AM)" <chenjun102@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"Xiangrui (Euler)" <rui.xiang@huawei.com>,
liuyanshi <liuyanshi@huawei.com>,
wuzengkun <wuzengkun@hisilicon.com>
Subject: Re: [question] insert ko failed because count_plts return 0 when CONFIG_RANDOMIZE_BASE is not set
Date: Thu, 25 Mar 2021 08:35:33 +0100 [thread overview]
Message-ID: <CAMj1kXGbwYqy3FCPuXw9nTtpU7MFduTr99Fo2A5cXe6VRvP1Xg@mail.gmail.com> (raw)
In-Reply-To: <54e5e0dbefa042b1b6a9c29fe9984897@huawei.com>
On Thu, 25 Mar 2021 at 07:22, chenjun (AM) <chenjun102@huawei.com> wrote:
>
> 在 2021/3/24 16:29, Ard Biesheuvel 写道:
> > On Wed, 24 Mar 2021 at 08:27, chenjun (AM) <chenjun102@huawei.com> wrote:
> >>
> >> Hi
> >>
> >> I make a Image for arm64 (without CONFIG_RANDOMIZE_BASE). And a ko (13M)
> >> can not be inserted.
> >>
> >
> > How many large modules have you loaded already? The module region is
> > only 128 MB, so if your modules are huge, you may run out of space.
> >
> > Please check the kernel VA address and the load address of the module,
> > and check whether they are more than 128 MB apart.
> >
>
> Thanks Ard
>
> I will check it.
>
> One more question, why is CONFIG_ARM64_MODULE_PLTS depended on
> CONFIG_RANDOMIZE_BASE?
>
Because modules should never go out of branching range if the
placement is not randomized and the total size of all modules does not
exceed 128 MB.
prev parent reply other threads:[~2021-03-25 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 7:27 [question] insert ko failed because count_plts return 0 when CONFIG_RANDOMIZE_BASE is not set chenjun (AM)
2021-03-24 8:29 ` Ard Biesheuvel
2021-03-25 6:21 ` chenjun (AM)
2021-03-25 7:35 ` Ard Biesheuvel [this message]
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=CAMj1kXGbwYqy3FCPuXw9nTtpU7MFduTr99Fo2A5cXe6VRvP1Xg@mail.gmail.com \
--to=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenjun102@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyanshi@huawei.com \
--cc=rui.xiang@huawei.com \
--cc=will.deacon@arm.com \
--cc=wuzengkun@hisilicon.com \
/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;
as well as URLs for NNTP newsgroup(s).