linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH 01/15] mm: add setup_initial_init_mm() helper
Date: Sat, 29 May 2021 18:54:50 +0800	[thread overview]
Message-ID: <20210529105504.180544-2-wangkefeng.wang@huawei.com> (raw)
In-Reply-To: <20210529105504.180544-1-wangkefeng.wang@huawei.com>

Add setup_initial_init_mm() helper to setup kernel text,
data and brk.

Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
---
 include/linux/mm_types.h | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 38a516ec7d98..ae4c2e95c80a 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -564,6 +564,16 @@ struct mm_struct {
 };
 
 extern struct mm_struct init_mm;
+static inline void setup_initial_init_mm(char *start_code,
+					 char *end_code,
+					 char *end_data,
+					 char *brk)
+{
+	init_mm.start_code = (unsigned long)start_code;
+	init_mm.end_code = (unsigned long)end_code;
+	init_mm.end_data = (unsigned long)end_data;
+	init_mm.brk = (unsigned long)brk;
+}
 
 /* Pointer magic because the dynamic array size confuses some compilers. */
 static inline void mm_init_cpumask(struct mm_struct *mm)
-- 
2.26.2


  reply	other threads:[~2021-05-29 10:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 10:54 [PATCH 00/15] init_mm: setup init_mm text/data/brk by new setup_initial_init_mm() helper Kefeng Wang
2021-05-29 10:54 ` Kefeng Wang [this message]
2021-05-31  7:45   ` [PATCH 01/15] mm: add " Geert Uytterhoeven
2021-05-31 13:42     ` Kefeng Wang
2021-05-29 10:54 ` [PATCH 02/15] arc: convert to setup_initial_init_mm() Kefeng Wang
2021-05-29 10:54 ` [PATCH 03/15] arm: " Kefeng Wang
2021-05-29 12:18   ` Russell King (Oracle)
2021-05-31  1:10     ` Kefeng Wang
2021-05-29 10:54 ` [PATCH 04/15] arm64: " Kefeng Wang
2021-05-29 10:54 ` [PATCH 05/15] csky: " Kefeng Wang
2021-05-30  0:23   ` Guo Ren
2021-05-29 10:54 ` [PATCH 06/15] h8300: " Kefeng Wang
2021-05-31  7:48   ` Geert Uytterhoeven
2021-05-29 10:54 ` [PATCH 07/15] m68k: " Kefeng Wang
2021-05-31  7:48   ` Geert Uytterhoeven
2021-06-02 13:13     ` Greg Ungerer
2021-05-29 10:54 ` [PATCH 08/15] nds32: " Kefeng Wang
2021-05-29 10:54 ` [PATCH 09/15] nios2: " Kefeng Wang
2021-05-29 10:54 ` [PATCH 10/15] openrisc: " Kefeng Wang
2021-05-29 13:48   ` Stafford Horne
2021-05-29 10:55 ` [PATCH 11/15] powerpc: " Kefeng Wang
2021-05-29 12:46   ` Santosh Sivaraj
2021-05-29 15:22     ` Christophe Leroy
2021-05-31  1:02       ` Kefeng Wang
2021-05-29 16:16   ` Christophe Leroy
2021-05-31  1:05     ` Kefeng Wang
2021-05-29 10:55 ` [PATCH 12/15] riscv: " Kefeng Wang
2021-05-29 10:55 ` [PATCH 13/15] s390: " Kefeng Wang
2021-05-29 10:55 ` [PATCH 14/15] sh: " Kefeng Wang
2021-05-29 10:55 ` [PATCH 15/15] x86: " Kefeng Wang

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=20210529105504.180544-2-wangkefeng.wang@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).