From: Catalin Marinas <catalin.marinas@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
will@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: defconfig: Enable memory hotplug and hotremove config
Date: Thu, 30 Jun 2022 11:49:50 +0100 [thread overview]
Message-ID: <Yr1/zr3LVzxLTlbG@arm.com> (raw)
In-Reply-To: <d4b409dc-b388-187d-4792-24909048a9ab@arm.com>
On Thu, Jun 30, 2022 at 12:40:44PM +0530, Anshuman Khandual wrote:
>
>
> On 6/29/22 15:05, Kefeng Wang wrote:
> > Let's enable ACPI_HMAT, ACPI_HOTPLUG_MEMORY, MEMORY_HOTPLUG
> > and MEMORY_HOTREMOVE for more test coverage, also there are
> > useful for heterogeneous memory scene.
> >
> > Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> > ---
> > v2: add ACPI_HMAT and update changelog too.
>
> In general, would like to see MEMORY_HOTPLUG/HOTREMOVE be selected
> here for better memory hotplug test coverage. But not sure whether
> there had been a rationale for not enabling this on defconfig.
Probably we didn't support the first defconfig was added and forgot
about it.
--
Catalin
_______________________________________________
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:[~2022-06-30 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 9:35 [PATCH v2] arm64: defconfig: Enable memory hotplug and hotremove config Kefeng Wang
2022-06-30 1:26 ` Kefeng Wang
2022-06-30 10:53 ` Catalin Marinas
2022-07-12 14:24 ` Kefeng Wang
2022-08-25 13:09 ` Kefeng Wang
2022-09-01 10:38 ` Catalin Marinas
2022-09-01 13:12 ` Kefeng Wang
2022-06-30 7:10 ` Anshuman Khandual
2022-06-30 10:49 ` Catalin Marinas [this message]
2022-09-21 12:47 ` 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=Yr1/zr3LVzxLTlbG@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangkefeng.wang@huawei.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 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).