From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Souptick Joarder <jrdr.linux@gmail.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: uclinux-h8-devel@lists.sourceforge.jp,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
X86 ML <x86@kernel.org>,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
Linux-MM <linux-mm@kvack.org>,
linux-m68k@lists.linux-m68k.org, openrisc@lists.librecores.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-snps-arc@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 resend 01/15] mm: add setup_initial_init_mm() helper
Date: Tue, 8 Jun 2021 16:57:13 +0200 [thread overview]
Message-ID: <34f88fdc-1842-7954-bccc-0142a8d66eea@csgroup.eu> (raw)
In-Reply-To: <CAFqt6zYmCQ=wxEjnOJ6fgJWYQyFajBuxWD=UT_D-WjWUS_4pcw@mail.gmail.com>
Le 08/06/2021 à 16:53, Souptick Joarder a écrit :
> On Tue, Jun 8, 2021 at 1:56 PM Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>>
>> Add setup_initial_init_mm() helper to setup kernel text,
>> data and brk.
>>
>> Cc: linux-snps-arc@lists.infradead.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-csky@vger.kernel.org
>> Cc: uclinux-h8-devel@lists.sourceforge.jp
>> Cc: linux-m68k@lists.linux-m68k.org
>> Cc: openrisc@lists.librecores.org
>> Cc: linuxppc-dev@lists.ozlabs.org
>> Cc: linux-riscv@lists.infradead.org
>> Cc: linux-sh@vger.kernel.org
>> Cc: linux-s390@vger.kernel.org
>> Cc: x86@kernel.org
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> include/linux/mm.h | 3 +++
>> mm/init-mm.c | 9 +++++++++
>> 2 files changed, 12 insertions(+)
>>
>> diff --git a/include/linux/mm.h b/include/linux/mm.h
>> index c274f75efcf9..02aa057540b7 100644
>> --- a/include/linux/mm.h
>> +++ b/include/linux/mm.h
>> @@ -244,6 +244,9 @@ int __add_to_page_cache_locked(struct page *page, struct address_space *mapping,
>>
>> #define lru_to_page(head) (list_entry((head)->prev, struct page, lru))
>>
>> +void setup_initial_init_mm(void *start_code, void *end_code,
>> + void *end_data, void *brk);
>> +
>
> Gentle query -> is there any limitation to add inline functions in
> setup_arch() functions ?
Kefeng just followed comment from Mike I guess, see
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20210604070633.32363-2-wangkefeng.wang@huawei.com/#2696253
Christophe
next prev parent reply other threads:[~2021-06-08 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210608083418.137226-1-wangkefeng.wang@huawei.com>
2021-06-08 8:34 ` [PATCH v3 resend 01/15] mm: add setup_initial_init_mm() helper Kefeng Wang
2021-06-08 14:53 ` Souptick Joarder
2021-06-08 14:57 ` Christophe Leroy [this message]
2021-06-08 15:14 ` Souptick Joarder
2021-06-08 8:34 ` [PATCH v3 resend 14/15] sh: convert to setup_initial_init_mm() 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=34f88fdc-1842-7954-bccc-0142a8d66eea@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=openrisc@lists.librecores.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=wangkefeng.wang@huawei.com \
--cc=x86@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).