From: Will Deacon <will@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Barry Song <song.bao.hua@hisilicon.com>,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
anshuman.khandual@arm.com, linuxarm@huawei.com
Subject: Re: [PATCH] arm64: mm: add support for memmap kernel parameters
Date: Wed, 18 Nov 2020 19:15:29 +0000 [thread overview]
Message-ID: <20201118191528.GA2680@willie-the-truck> (raw)
In-Reply-To: <20201118173854.GA8537@kernel.org>
On Wed, Nov 18, 2020 at 07:38:54PM +0200, Mike Rapoport wrote:
> On Wed, Nov 18, 2020 at 07:33:14PM +1300, Barry Song wrote:
> > memmap should be an useful kernel parameter which has been supported by
> > x86, mips and xtensa.
>
> Why is this parameter should be useful for ARM64?
> My understanding is that it is required only to work around really
> broken bootloaders, isn't it?
Agreed, I can't see this being something we really want to support. If it
turns out that it is generally useful, then the implementation should
probably be somewhere outside of arch/ where I don't have to look at it :)
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Barry Song <song.bao.hua@hisilicon.com>,
anshuman.khandual@arm.com, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: mm: add support for memmap kernel parameters
Date: Wed, 18 Nov 2020 19:15:29 +0000 [thread overview]
Message-ID: <20201118191528.GA2680@willie-the-truck> (raw)
In-Reply-To: <20201118173854.GA8537@kernel.org>
On Wed, Nov 18, 2020 at 07:38:54PM +0200, Mike Rapoport wrote:
> On Wed, Nov 18, 2020 at 07:33:14PM +1300, Barry Song wrote:
> > memmap should be an useful kernel parameter which has been supported by
> > x86, mips and xtensa.
>
> Why is this parameter should be useful for ARM64?
> My understanding is that it is required only to work around really
> broken bootloaders, isn't it?
Agreed, I can't see this being something we really want to support. If it
turns out that it is generally useful, then the implementation should
probably be somewhere outside of arch/ where I don't have to look at it :)
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-18 19:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 6:33 [PATCH] arm64: mm: add support for memmap kernel parameters Barry Song
2020-11-18 6:33 ` Barry Song
2020-11-18 17:38 ` Mike Rapoport
2020-11-18 17:38 ` Mike Rapoport
2020-11-18 19:15 ` Will Deacon [this message]
2020-11-18 19:15 ` Will Deacon
2020-11-18 20:25 ` Song Bao Hua (Barry Song)
2020-11-18 20:25 ` Song Bao Hua (Barry Song)
2020-11-18 22:38 ` Ard Biesheuvel
2020-11-18 22:38 ` Ard Biesheuvel
2020-11-18 23:55 ` Song Bao Hua (Barry Song)
2020-11-18 23:55 ` Song Bao Hua (Barry Song)
2020-11-19 7:57 ` Mike Rapoport
2020-11-19 7:57 ` Mike Rapoport
2020-11-19 8:37 ` Song Bao Hua (Barry Song)
2020-11-19 8:37 ` Song Bao Hua (Barry Song)
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=20201118191528.GA2680@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rppt@kernel.org \
--cc=song.bao.hua@hisilicon.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 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.