From: Christoph Hellwig <hch@lst.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Linux Memory Management List <linux-mm@kvack.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 1/4] of/fdt: Update zone_dma_bits when running in bcm2711
Date: Mon, 12 Oct 2020 08:47:15 +0200 [thread overview]
Message-ID: <20201012064715.GA2548@lst.de> (raw)
In-Reply-To: <20201009171051.GL23638@gaia>
On Fri, Oct 09, 2020 at 06:10:52PM +0100, Catalin Marinas wrote:
> kdump wants DMA-able memory and,
DMAable by whom? The only way to guranteed DMAable memory is to use
the DMA memory allocator(s) and pass a specific device to them. Everyting
else is just fundamentally broken. Note that even when device is not
DMAable we can still use swiotlb to access it.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Linux Memory Management List <linux-mm@kvack.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 1/4] of/fdt: Update zone_dma_bits when running in bcm2711
Date: Mon, 12 Oct 2020 08:47:15 +0200 [thread overview]
Message-ID: <20201012064715.GA2548@lst.de> (raw)
In-Reply-To: <20201009171051.GL23638@gaia>
On Fri, Oct 09, 2020 at 06:10:52PM +0100, Catalin Marinas wrote:
> kdump wants DMA-able memory and,
DMAable by whom? The only way to guranteed DMAable memory is to use
the DMA memory allocator(s) and pass a specific device to them. Everyting
else is just fundamentally broken. Note that even when device is not
DMAable we can still use swiotlb to access it.
_______________________________________________
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: Christoph Hellwig <hch@lst.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Will Deacon <will@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
Frank Rowand <frowand.list@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 1/4] of/fdt: Update zone_dma_bits when running in bcm2711
Date: Mon, 12 Oct 2020 08:47:15 +0200 [thread overview]
Message-ID: <20201012064715.GA2548@lst.de> (raw)
In-Reply-To: <20201009171051.GL23638@gaia>
On Fri, Oct 09, 2020 at 06:10:52PM +0100, Catalin Marinas wrote:
> kdump wants DMA-able memory and,
DMAable by whom? The only way to guranteed DMAable memory is to use
the DMA memory allocator(s) and pass a specific device to them. Everyting
else is just fundamentally broken. Note that even when device is not
DMAable we can still use swiotlb to access it.
next prev parent reply other threads:[~2020-10-12 6:47 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 16:17 [PATCH 0/4] arm64: Default to 32-bit wide ZONE_DMA Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` [PATCH 1/4] of/fdt: Update zone_dma_bits when running in bcm2711 Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 17:15 ` Catalin Marinas
2020-10-01 17:15 ` Catalin Marinas
2020-10-01 17:15 ` Catalin Marinas
2020-10-01 17:23 ` Catalin Marinas
2020-10-01 17:23 ` Catalin Marinas
2020-10-01 17:23 ` Catalin Marinas
2020-10-01 17:31 ` Nicolas Saenz Julienne
2020-10-01 17:31 ` Nicolas Saenz Julienne
2020-10-01 17:31 ` Nicolas Saenz Julienne
2020-10-01 20:02 ` Rob Herring
2020-10-01 20:02 ` Rob Herring
2020-10-01 20:02 ` Rob Herring
2020-10-02 11:55 ` Catalin Marinas
2020-10-02 11:55 ` Catalin Marinas
2020-10-02 11:55 ` Catalin Marinas
2020-10-08 10:05 ` Nicolas Saenz Julienne
2020-10-08 10:05 ` Nicolas Saenz Julienne
2020-10-08 10:05 ` Nicolas Saenz Julienne
2020-10-08 10:13 ` Catalin Marinas
2020-10-08 10:13 ` Catalin Marinas
2020-10-08 10:13 ` Catalin Marinas
2020-10-08 19:43 ` Ard Biesheuvel
2020-10-08 19:43 ` Ard Biesheuvel
2020-10-08 19:43 ` Ard Biesheuvel
2020-10-09 3:59 ` Jeremy Linton
2020-10-09 3:59 ` Jeremy Linton
2020-10-09 3:59 ` Jeremy Linton
2020-10-09 8:37 ` Nicolas Saenz Julienne
2020-10-09 8:37 ` Nicolas Saenz Julienne
2020-10-09 8:37 ` Nicolas Saenz Julienne
2020-10-09 7:10 ` Christoph Hellwig
2020-10-09 7:10 ` Christoph Hellwig
2020-10-09 7:10 ` Christoph Hellwig
2020-10-09 7:37 ` Ard Biesheuvel
2020-10-09 7:37 ` Ard Biesheuvel
2020-10-09 7:37 ` Ard Biesheuvel
2020-10-09 8:36 ` Nicolas Saenz Julienne
2020-10-09 8:36 ` Nicolas Saenz Julienne
2020-10-09 8:36 ` Nicolas Saenz Julienne
2020-10-09 9:13 ` Ard Biesheuvel
2020-10-09 9:13 ` Ard Biesheuvel
2020-10-09 9:13 ` Ard Biesheuvel
2020-10-09 13:33 ` Nicolas Saenz Julienne
2020-10-09 13:33 ` Nicolas Saenz Julienne
2020-10-09 13:33 ` Nicolas Saenz Julienne
2020-10-09 15:24 ` Lorenzo Pieralisi
2020-10-09 15:24 ` Lorenzo Pieralisi
2020-10-09 15:24 ` Lorenzo Pieralisi
2020-10-09 16:23 ` Ard Biesheuvel
2020-10-09 16:23 ` Ard Biesheuvel
2020-10-09 16:23 ` Ard Biesheuvel
2020-10-09 17:10 ` Catalin Marinas
2020-10-09 17:10 ` Catalin Marinas
2020-10-09 17:10 ` Catalin Marinas
2020-10-10 10:36 ` Ard Biesheuvel
2020-10-10 10:36 ` Ard Biesheuvel
2020-10-10 10:36 ` Ard Biesheuvel
2020-10-10 10:53 ` Nicolas Saenz Julienne
2020-10-10 10:53 ` Nicolas Saenz Julienne
2020-10-10 10:53 ` Nicolas Saenz Julienne
2020-10-10 12:38 ` Catalin Marinas
2020-10-10 12:38 ` Catalin Marinas
2020-10-10 12:38 ` Catalin Marinas
2020-10-12 6:47 ` Christoph Hellwig [this message]
2020-10-12 6:47 ` Christoph Hellwig
2020-10-12 6:47 ` Christoph Hellwig
2020-10-12 8:47 ` Catalin Marinas
2020-10-12 8:47 ` Catalin Marinas
2020-10-12 8:47 ` Catalin Marinas
2020-10-02 9:05 ` kernel test robot
2020-10-02 9:05 ` kernel test robot
2020-10-02 9:05 ` kernel test robot
2020-10-01 16:17 ` [PATCH 2/4] dma-direct: Turn zone_dma_bits default value into a define Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` [PATCH 3/4] arm64: Default to 32-bit ZONE_DMA Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 17:19 ` Catalin Marinas
2020-10-01 17:19 ` Catalin Marinas
2020-10-01 17:19 ` Catalin Marinas
2020-10-01 16:17 ` [PATCH 4/4] mm: Update DMA zones description Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne
2020-10-01 17:19 ` Catalin Marinas
2020-10-01 17:19 ` Catalin Marinas
2020-10-01 17:19 ` 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=20201012064715.GA2548@lst.de \
--to=hch@lst.de \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--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 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.