From: xieyisheng1@huawei.com (Yisheng Xie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] arm64/mm: handle memmap kernel option
Date: Mon, 27 Feb 2017 11:48:50 +0800 [thread overview]
Message-ID: <ab8d4b0a-dfe5-629f-5ead-3c7e907509fa@huawei.com> (raw)
In-Reply-To: <CAKv+Gu9j_4kSVAPrddsdcDiW+MWMTweHPe9bthf4=n4jLt2NZw@mail.gmail.com>
Hi Ard,
Thanks for comment.
On 2017/2/26 18:46, Ard Biesheuvel wrote:
> On 25 February 2017 at 06:47, Yisheng Xie <xieyisheng1@huawei.com> wrote:
>> When use device tree mode, user can reserve memory by changes the dts,
>> however, when boot with ACPI, user cannot reserve memory except by
>> changing the ACPI table in BIOS, which is not so convenient.
>>
>> To make user reserve memory for some specific use more convenient,
>> this patch implement the following memmap variants:
>> - memmap=nn[KMG]$ss[KMG]: mark specified memory as reserved;
>> - memmap=nn[KMG]@ss[KMG]: force usage of a specific region of memory;
>>
>> Reported-by: Bob Dong <dongbo4@huawei.com>
>> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
>
> Could you explain which problem you are solving here? ACPI implies
> UEFI on arm64, and so these reservations could be made by a boot
> component instead, if it requires a fixed memory reservation. If this
> is a reservation for, e.g., OP-TEE, we should not rely on the command
> line to communicate this information.
>
We just want to reserve some memory for a driver and I just not so familiar
with how to reserve memory with UEFI. So doubt about whether it is suitable
to reserve memory with cmdline like "memmap=xxx", which had appeared in x86
for a long time.
Thanks
Yisheng Xie
next prev parent reply other threads:[~2017-02-27 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 6:47 [PATCH RFC] arm64/mm: handle memmap kernel option Yisheng Xie
2017-02-26 10:46 ` Ard Biesheuvel
2017-02-27 3:48 ` Yisheng Xie [this message]
2017-02-27 8:48 ` Mark Rutland
2017-02-27 10:24 ` Yisheng Xie
2017-02-27 11:42 ` Ard Biesheuvel
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=ab8d4b0a-dfe5-629f-5ead-3c7e907509fa@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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