From: Romain Dolbeau <romain.dolbeau@european-processor-initiative.eu>
To: Alex Ghiti <alex@ghiti.fr>, Anup Patel <anup@brainfault.org>,
Aurelien Jarno <aurelien@aurel32.net>
Cc: Vincent Chen <vincent.chen@sifive.com>,
Carlos Eduardo de Paula <me@carlosedp.com>,
Paul Walmsley <paul@pwsan.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
David Abdurachmanov <david.abdurachmanov@gmail.com>
Subject: Re: Error on loading some network Kernel modules
Date: Sun, 2 Feb 2020 17:27:38 +0100 [thread overview]
Message-ID: <33c9a276-6212-115c-c7c9-e62244f13c76@european-processor-initiative.eu> (raw)
In-Reply-To: <d868acf5-7242-93dc-0051-f97e64dc4387@ghiti.fr>
On 2020-02-01 14:59, Alex Ghiti wrote:
> Why restrict to 128M whereas we have 2GB offset available to the end of
> the kernel ?
Isn't that 2 GiB offset to whatever the module requires in the kernel,
rather than to the end of the kernel space?
Is there some guarantee that symbols accessible by modules are at the
end of the kernel? If so, wouldn't the maximum offset for this patch
still be (2 GiB - <total size of accessible symbols>)?
Cordially,
--
Romain Dolbeau
next prev parent reply other threads:[~2020-02-02 16:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 19:22 Error on loading some network Kernel modules Carlos Eduardo de Paula
2020-01-30 3:00 ` Paul Walmsley
2020-01-30 16:20 ` David Abdurachmanov
2020-01-31 14:12 ` Carlos Eduardo de Paula
2020-01-31 20:11 ` Aurelien Jarno
2020-02-01 7:52 ` Anup Patel
2020-02-01 13:59 ` Alex Ghiti
2020-02-02 14:10 ` Anup Patel
2020-02-02 15:21 ` Troy Benjegerdes
2020-02-02 16:27 ` Romain Dolbeau [this message]
2020-02-03 10:04 ` Vincent Chen
2020-02-04 3:55 ` Zong Li
2020-02-04 6:50 ` Alex Ghiti
2020-02-04 7:19 ` Zong Li
2020-02-04 9:32 ` Alexandre Ghiti
2020-02-04 10:46 ` Vincent Chen
2020-02-04 11:30 ` Anup Patel
2020-02-04 14:03 ` Vincent Chen
2020-02-04 19:10 ` Alex Ghiti
[not found] ` <a55f265e-71b2-5ebb-b079-6345007a442e@ghiti.fr>
2020-02-05 3:22 ` Vincent Chen
2020-02-05 4:24 ` Anup Patel
2020-02-05 10:37 ` Vincent Chen
2020-02-07 14:39 ` Vincent Chen
2020-02-07 14:51 ` Vincent Chen
2020-02-10 6:37 ` Alex Ghiti
2020-02-10 9:53 ` Vincent Chen
2020-02-19 6:46 ` Alex Ghiti
2020-02-19 7:30 ` Vincent Chen
2020-02-04 17:48 ` Romain Dolbeau
2020-02-03 20:57 ` Alex Ghiti
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=33c9a276-6212-115c-c7c9-e62244f13c76@european-processor-initiative.eu \
--to=romain.dolbeau@european-processor-initiative.eu \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aurelien@aurel32.net \
--cc=david.abdurachmanov@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=me@carlosedp.com \
--cc=paul@pwsan.com \
--cc=vincent.chen@sifive.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).