From: Xishi Qiu <qiuxishi@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
chenjie6@huawei.com
Subject: arm64: why set SECTION_SIZE_BITS to 1G size?
Date: Thu, 11 Aug 2016 17:44:46 +0800 [thread overview]
Message-ID: <57AC490E.4080204@huawei.com> (raw)
Hi everyone:
arm64:
SECTION_SIZE_BITS 30 -----1G
The memory hotplug(add_memory -->check_hotplug_memory_range)
must be aligned with section.So I can not add mem with 64M ...
Can I modify the SECTION_SIZE_BITS to 26?
Thanks,
Xishi Qiu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Xishi Qiu <qiuxishi@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, <chenjie6@huawei.com>
Subject: arm64: why set SECTION_SIZE_BITS to 1G size?
Date: Thu, 11 Aug 2016 17:44:46 +0800 [thread overview]
Message-ID: <57AC490E.4080204@huawei.com> (raw)
Hi everyone:
arm64:
SECTION_SIZE_BITS 30 -----1G
The memory hotplug(add_memory -->check_hotplug_memory_range)
must be aligned with section.So I can not add mem with 64M ...
Can I modify the SECTION_SIZE_BITS to 26?
Thanks,
Xishi Qiu
next reply other threads:[~2016-08-11 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 9:44 Xishi Qiu [this message]
2016-08-11 9:44 ` arm64: why set SECTION_SIZE_BITS to 1G size? Xishi Qiu
2016-08-11 10:07 ` Catalin Marinas
2016-08-11 10:07 ` Catalin Marinas
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=57AC490E.4080204@huawei.com \
--to=qiuxishi@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=chenjie6@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.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.