From: Will Deacon <will@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: song.bao.hua@hisilicon.com, xiexiuqi@huawei.com,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
nsaenzjulienne@suse.de, huawei.libin@huawei.com,
akpm@linux-foundation.org, ardb@kernel.org, rppt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: mm: fix kdump broken with ZONE_DMA reintroduced
Date: Wed, 20 Jan 2021 12:40:55 +0000 [thread overview]
Message-ID: <20210120124054.GA19504@willie-the-truck> (raw)
In-Reply-To: <20201226033557.116251-1-chenzhou10@huawei.com>
On Sat, Dec 26, 2020 at 11:35:55AM +0800, Chen Zhou wrote:
> If the memory reserved for crash dump kernel falled in ZONE_DMA32,
> the devices in crash dump kernel need to use ZONE_DMA will alloc fail.
>
> Fix this by reserving low memory in ZONE_DMA if CONFIG_ZONE_DMA is
> enabled, otherwise, reserving in ZONE_DMA32.
>
> Patch 1 updates the comments about the ZONE_DMA.
> Patch 2 fix kdump broken.
>
> Chen Zhou (2):
> arm64: mm: update the comments about ZONE_DMA
> arm64: mm: fix kdump broken with ZONE_DMA reintroduced
Please can you repost this if it is still needed after the changes that
landed in -rc4?
Will
_______________________________________________
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: Will Deacon <will@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: catalin.marinas@arm.com, ardb@kernel.org,
akpm@linux-foundation.org, rppt@kernel.org,
nsaenzjulienne@suse.de, song.bao.hua@hisilicon.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, huawei.libin@huawei.com,
xiexiuqi@huawei.com
Subject: Re: [PATCH 0/2] arm64: mm: fix kdump broken with ZONE_DMA reintroduced
Date: Wed, 20 Jan 2021 12:40:55 +0000 [thread overview]
Message-ID: <20210120124054.GA19504@willie-the-truck> (raw)
In-Reply-To: <20201226033557.116251-1-chenzhou10@huawei.com>
On Sat, Dec 26, 2020 at 11:35:55AM +0800, Chen Zhou wrote:
> If the memory reserved for crash dump kernel falled in ZONE_DMA32,
> the devices in crash dump kernel need to use ZONE_DMA will alloc fail.
>
> Fix this by reserving low memory in ZONE_DMA if CONFIG_ZONE_DMA is
> enabled, otherwise, reserving in ZONE_DMA32.
>
> Patch 1 updates the comments about the ZONE_DMA.
> Patch 2 fix kdump broken.
>
> Chen Zhou (2):
> arm64: mm: update the comments about ZONE_DMA
> arm64: mm: fix kdump broken with ZONE_DMA reintroduced
Please can you repost this if it is still needed after the changes that
landed in -rc4?
Will
next prev parent reply other threads:[~2021-01-20 12:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 3:35 [PATCH 0/2] arm64: mm: fix kdump broken with ZONE_DMA reintroduced Chen Zhou
2020-12-26 3:35 ` Chen Zhou
2020-12-26 3:35 ` [PATCH 1/2] arm64: mm: update the comments about ZONE_DMA Chen Zhou
2020-12-26 3:35 ` Chen Zhou
2020-12-26 10:35 ` Nicolas Saenz Julienne
2020-12-26 10:35 ` Nicolas Saenz Julienne
2020-12-26 3:35 ` [PATCH 2/2] arm64: mm: fix kdump broken with ZONE_DMA reintroduced Chen Zhou
2020-12-26 3:35 ` Chen Zhou
2020-12-26 10:34 ` Nicolas Saenz Julienne
2020-12-26 10:34 ` Nicolas Saenz Julienne
2020-12-28 7:32 ` chenzhou
2020-12-28 7:32 ` chenzhou
2021-01-07 18:34 ` Catalin Marinas
2021-01-07 18:34 ` Catalin Marinas
2021-01-07 14:25 ` Catalin Marinas
2021-01-07 14:25 ` Catalin Marinas
2021-01-08 1:09 ` chenzhou
2021-01-08 1:09 ` chenzhou
2021-01-20 12:40 ` Will Deacon [this message]
2021-01-20 12:40 ` [PATCH 0/2] " Will Deacon
2021-01-20 13:07 ` Catalin Marinas
2021-01-20 13:07 ` Catalin Marinas
2021-01-21 2:37 ` chenzhou
2021-01-21 2:37 ` chenzhou
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=20210120124054.GA19504@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenzhou10@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=rppt@kernel.org \
--cc=song.bao.hua@hisilicon.com \
--cc=xiexiuqi@huawei.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.