From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Chen Zhou <chenzhou10@huawei.com>,
catalin.marinas@arm.com, will@kernel.org
Cc: ardb@kernel.org, akpm@linux-foundation.org, rppt@kernel.org,
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 1/2] arm64: mm: update the comments about ZONE_DMA
Date: Sat, 26 Dec 2020 11:35:58 +0100 [thread overview]
Message-ID: <407ae3b1d7da3d1e7aa3e815e1af27832b914aa5.camel@suse.de> (raw)
In-Reply-To: <20201226033557.116251-2-chenzhou10@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
On Sat, 2020-12-26 at 11:35 +0800, Chen Zhou wrote:
> Since patchset "arm64: Default to 32-bit wide ZONE_DMA", ZONE_DMA's
> size is fine-tuned. In the absence of addressing limited masters,
> ZONE_DMA will span the whole 32-bit address space, otherwise, in
> the case of the Raspberry Pi 4, it'll only span the 30-bit address
> space. Update the comments.
>
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> ---
Reviewed-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> arch/arm64/mm/init.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index 75addb36354a..7b9809e39927 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -53,10 +53,11 @@ s64 memstart_addr __ro_after_init = -1;
> EXPORT_SYMBOL(memstart_addr);
>
>
> /*
> - * We create both ZONE_DMA and ZONE_DMA32. ZONE_DMA covers the first 1G of
> - * memory as some devices, namely the Raspberry Pi 4, have peripherals with
> - * this limited view of the memory. ZONE_DMA32 will cover the rest of the 32
> - * bit addressable memory area.
> + * We create both ZONE_DMA and ZONE_DMA32. ZONE_DMA's size is fine-tuned.
> + * In the absence of addressing limited masters, ZONE_DMA will span the
> + * whole 32-bit address space, otherwise, in the case of the Raspberry Pi 4,
> + * it'll only span the 30-bit address space. ZONE_DMA32 will cover the rest
> + * of the 32 bit addressable memory area.
> */
> phys_addr_t arm64_dma_phys_limit __ro_after_init;
> static phys_addr_t arm64_dma32_phys_limit __ro_after_init;
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-26 10:36 UTC|newest]
Thread overview: 12+ 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 ` [PATCH 1/2] arm64: mm: update the comments about ZONE_DMA Chen Zhou
2020-12-26 10:35 ` Nicolas Saenz Julienne [this message]
2020-12-26 3:35 ` [PATCH 2/2] arm64: mm: fix kdump broken with ZONE_DMA reintroduced Chen Zhou
2020-12-26 10:34 ` Nicolas Saenz Julienne
2020-12-28 7:32 ` chenzhou
2021-01-07 18:34 ` Catalin Marinas
2021-01-07 14:25 ` Catalin Marinas
2021-01-08 1:09 ` chenzhou
2021-01-20 12:40 ` [PATCH 0/2] " Will Deacon
2021-01-20 13:07 ` Catalin Marinas
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=407ae3b1d7da3d1e7aa3e815e1af27832b914aa5.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--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=rppt@kernel.org \
--cc=song.bao.hua@hisilicon.com \
--cc=will@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®