From: Aaron Tomlin <atomlin@redhat.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kgdb-bugreport@lists.sourceforge.net, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-modules@vger.kernel.org
Subject: Re: [PATCH v5 1/6] module: Always have struct mod_tree_root
Date: Tue, 22 Feb 2022 17:57:05 +0000 [thread overview]
Message-ID: <20220222175705.ryqmhhrpokx7xbgv@ava.usersys.com> (raw)
In-Reply-To: <c9584f48abce748e62e65e6757ceb23800f15380.1645541930.git.christophe.leroy@csgroup.eu>
On Tue 2022-02-22 16:00 +0100, Christophe Leroy wrote:
> In order to separate text and data, we need to setup
> two rb trees.
>
> This means that struct mod_tree_root is required even without
> MODULES_TREE_LOOKUP.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> kernel/module/internal.h | 4 +++-
> kernel/module/main.c | 5 -----
> 2 files changed, 3 insertions(+), 6 deletions(-)
Reviewed-by: Aaron Tomlin <atomlin@atomlin.com>
--
Aaron Tomlin
next prev parent reply other threads:[~2022-02-22 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 15:00 [PATCH v5 0/6] Allocate module text and data separately Christophe Leroy
2022-02-22 15:00 ` [PATCH v5 1/6] module: Always have struct mod_tree_root Christophe Leroy
2022-02-22 17:57 ` Aaron Tomlin [this message]
2022-02-22 15:00 ` [PATCH v5 2/6] module: Prepare for handling several RB trees Christophe Leroy
2022-02-22 15:00 ` [PATCH v5 3/6] module: Introduce data_layout Christophe Leroy
2022-02-22 15:00 ` [PATCH v5 4/6] module: Add CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC Christophe Leroy
2022-02-22 15:00 ` [PATCH v5 5/6] module: Remove module_addr_min and module_addr_max Christophe Leroy
2022-02-22 15:00 ` [PATCH v5 6/6] powerpc: Select ARCH_WANTS_MODULES_DATA_IN_VMALLOC on book3s/32 and 8xx Christophe Leroy
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=20220222175705.ryqmhhrpokx7xbgv@ava.usersys.com \
--to=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcgrof@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