From: Jeremy Linton <jeremy.linton@arm.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
robh+dt@kernel.org, catalin.marinas@arm.com, hch@lst.de,
ardb@kernel.org, linux-kernel@vger.kernel.org
Cc: robin.murphy@arm.com, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
will@kernel.org, lorenzo.pieralisi@arm.com, guohanjun@huawei.com,
linux-acpi@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v4 0/7] arm64: Default to 32-bit wide ZONE_DMA
Date: Fri, 23 Oct 2020 14:05:45 -0500 [thread overview]
Message-ID: <9bccc5ef-9457-044b-7193-d002a395e461@arm.com> (raw)
In-Reply-To: <20201021123437.21538-1-nsaenzjulienne@suse.de>
Hi,
On 10/21/20 7:34 AM, Nicolas Saenz Julienne wrote:
> Using two distinct DMA zones turned out to be problematic. Here's an
> attempt go back to a saner default.
>
> I tested this on both a RPi4 and QEMU.
I've tested this in ACPI mode on the rpi4 (4+8G with/without the 3G
limiter) as well, with Ard's IORT patch. Nothing seems to have regressed.
Thanks,
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
>
> ---
>
> Changes since v3:
> - Drop patch adding define in dma-mapping
> - Address small review changes
> - Update Ard's patch
> - Add new patch removing examples from mmzone.h
>
> Changes since v2:
> - Introduce Ard's patch
> - Improve OF dma-ranges parsing function
> - Add unit test for OF function
> - Address small changes
> - Move crashkernel reservation later in boot process
>
> Changes since v1:
> - Parse dma-ranges instead of using machine compatible string
>
> Ard Biesheuvel (1):
> arm64: mm: Set ZONE_DMA size based on early IORT scan
>
> Nicolas Saenz Julienne (6):
> arm64: mm: Move reserve_crashkernel() into mem_init()
> arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()
> of/address: Introduce of_dma_get_max_cpu_address()
> of: unittest: Add test for of_dma_get_max_cpu_address()
> arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges
> mm: Remove examples from enum zone_type comment
>
> arch/arm64/mm/init.c | 16 ++++++------
> drivers/acpi/arm64/iort.c | 52 +++++++++++++++++++++++++++++++++++++++
> drivers/of/address.c | 42 +++++++++++++++++++++++++++++++
> drivers/of/unittest.c | 18 ++++++++++++++
> include/linux/acpi_iort.h | 4 +++
> include/linux/mmzone.h | 20 ---------------
> include/linux/of.h | 7 ++++++
> 7 files changed, 130 insertions(+), 29 deletions(-)
>
next prev parent reply other threads:[~2020-10-23 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 12:34 [PATCH v4 0/7] arm64: Default to 32-bit wide ZONE_DMA Nicolas Saenz Julienne
2020-10-21 12:34 ` [PATCH v4 7/7] mm: Remove examples from enum zone_type comment Nicolas Saenz Julienne
2020-10-23 6:49 ` Christoph Hellwig
2020-10-23 19:05 ` Jeremy Linton [this message]
2020-10-27 11:50 ` [PATCH v4 0/7] arm64: Default to 32-bit wide ZONE_DMA Nicolas Saenz Julienne
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=9bccc5ef-9457-044b-7193-d002a395e461@arm.com \
--to=jeremy.linton@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=guohanjun@huawei.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nsaenzjulienne@suse.de \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.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).