From: Mike Rapoport <rppt@kernel.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Ard Biesheuvel <ardb@kernel.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr
Date: Thu, 16 Dec 2021 16:19:15 +0200 [thread overview]
Message-ID: <YbtK42WAk3aL/Zqr@kernel.org> (raw)
In-Reply-To: <DU0PR04MB941762839A98B9BB140876E688769@DU0PR04MB9417.eurprd04.prod.outlook.com>
On Wed, Dec 15, 2021 at 12:05:36PM +0000, Peng Fan wrote:
> > Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr
> >
> > > > > > > If pass "mem=1024MB", the actually max addr will be
> > > > > > > 0x81000000. However if need the max addr be 0x80000000,
> > > > > > > mem=1008MB should be used.
> > > > > > >
>
> BTW, do you think max_addr would be an option be added to memblock
> common code mm/memblock.c?
You have a working solution with mem=1008MB, I don't see a need for
additional kernel parameter.
--
Sincerely yours,
Mike.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Ard Biesheuvel <ardb@kernel.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr
Date: Thu, 16 Dec 2021 16:19:15 +0200 [thread overview]
Message-ID: <YbtK42WAk3aL/Zqr@kernel.org> (raw)
In-Reply-To: <DU0PR04MB941762839A98B9BB140876E688769@DU0PR04MB9417.eurprd04.prod.outlook.com>
On Wed, Dec 15, 2021 at 12:05:36PM +0000, Peng Fan wrote:
> > Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr
> >
> > > > > > > If pass "mem=1024MB", the actually max addr will be
> > > > > > > 0x81000000. However if need the max addr be 0x80000000,
> > > > > > > mem=1008MB should be used.
> > > > > > >
>
> BTW, do you think max_addr would be an option be added to memblock
> common code mm/memblock.c?
You have a working solution with mem=1008MB, I don't see a need for
additional kernel parameter.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-12-16 14:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 6:45 [PATCH 1/2] arm64: mm: apply __ro_after_init to memory_limit Peng Fan (OSS)
2021-12-15 6:45 ` Peng Fan (OSS)
2021-12-15 6:45 ` [PATCH 2/2] arm64: mm: support bootparam max_addr Peng Fan (OSS)
2021-12-15 6:45 ` Peng Fan (OSS)
2021-12-15 7:32 ` Ard Biesheuvel
2021-12-15 7:32 ` Ard Biesheuvel
2021-12-15 7:59 ` Peng Fan
2021-12-15 7:59 ` Peng Fan
2021-12-15 9:24 ` Mike Rapoport
2021-12-15 9:24 ` Mike Rapoport
2021-12-15 9:30 ` Peng Fan
2021-12-15 9:30 ` Peng Fan
2021-12-15 9:53 ` Mike Rapoport
2021-12-15 9:53 ` Mike Rapoport
2021-12-15 12:05 ` Peng Fan
2021-12-15 12:05 ` Peng Fan
2021-12-16 14:19 ` Mike Rapoport [this message]
2021-12-16 14:19 ` Mike Rapoport
2021-12-15 7:30 ` [PATCH 1/2] arm64: mm: apply __ro_after_init to memory_limit Ard Biesheuvel
2021-12-15 7:30 ` Ard Biesheuvel
2021-12-15 10:02 ` David Hildenbrand
2021-12-15 10:02 ` David Hildenbrand
2022-01-20 15:56 ` (subset) " Catalin Marinas
2022-01-20 15:56 ` Catalin Marinas
2022-01-21 2:28 ` Anshuman Khandual
2022-01-21 2:28 ` Anshuman Khandual
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=YbtK42WAk3aL/Zqr@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=geert+renesas@glider.be \
--cc=jan.kiszka@siemens.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.