From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> To: catalin.marinas@arm.com, linux-kernel@vger.kernel.org Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>, devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 0/2] arm64: Fix CMA/crashkernel reservation Date: Thu, 7 Nov 2019 10:56:09 +0100 [thread overview] Message-ID: <20191107095611.18429-1-nsaenzjulienne@suse.de> (raw) As pointed out by Qian Cai[1] the series enabling ZONE_DMA in arm64 breaks CMA/crashkernel reservations on large devices, as it changed its default placement. After discussing it with Catalin Marinas we're restoring the old behavior. The Raspberry Pi 4, being the only device that needs CMA and crashkernel in ZONE_DMA will explicitly do so trough it's device tree. [1] https://lkml.org/lkml/2019/10/21/725 --- Changes since v1: - Move CMA area registration into bcm2711.dtsi Changes since v1: - s/Raspberry Pi/bcm2711 in bcm2711.dtsi Nicolas Saenz Julienne (2): ARM: dts: bcm2711: force CMA into first GB of memory arm64: mm: reserve CMA and crashkernel in ZONE_DMA32 arch/arm/boot/dts/bcm2711.dtsi | 20 ++++++++++++++++++++ arch/arm64/mm/init.c | 4 ++-- 2 files changed, 22 insertions(+), 2 deletions(-) -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> To: catalin.marinas@arm.com, linux-kernel@vger.kernel.org Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Subject: [PATCH v3 0/2] arm64: Fix CMA/crashkernel reservation Date: Thu, 7 Nov 2019 10:56:09 +0100 [thread overview] Message-ID: <20191107095611.18429-1-nsaenzjulienne@suse.de> (raw) As pointed out by Qian Cai[1] the series enabling ZONE_DMA in arm64 breaks CMA/crashkernel reservations on large devices, as it changed its default placement. After discussing it with Catalin Marinas we're restoring the old behavior. The Raspberry Pi 4, being the only device that needs CMA and crashkernel in ZONE_DMA will explicitly do so trough it's device tree. [1] https://lkml.org/lkml/2019/10/21/725 --- Changes since v1: - Move CMA area registration into bcm2711.dtsi Changes since v1: - s/Raspberry Pi/bcm2711 in bcm2711.dtsi Nicolas Saenz Julienne (2): ARM: dts: bcm2711: force CMA into first GB of memory arm64: mm: reserve CMA and crashkernel in ZONE_DMA32 arch/arm/boot/dts/bcm2711.dtsi | 20 ++++++++++++++++++++ arch/arm64/mm/init.c | 4 ++-- 2 files changed, 22 insertions(+), 2 deletions(-) -- 2.23.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-07 9:56 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-07 9:56 Nicolas Saenz Julienne [this message] 2019-11-07 9:56 ` [PATCH v3 0/2] arm64: Fix CMA/crashkernel reservation Nicolas Saenz Julienne 2019-11-07 9:56 ` [PATCH v3 1/2] ARM: dts: bcm2711: force CMA into first GB of memory Nicolas Saenz Julienne 2019-11-07 9:56 ` Nicolas Saenz Julienne 2019-11-07 11:20 ` Catalin Marinas 2019-11-07 11:20 ` Catalin Marinas 2019-11-07 17:59 ` Florian Fainelli 2019-11-07 17:59 ` Florian Fainelli 2019-11-07 19:09 ` Stefan Wahren 2019-11-07 19:09 ` Stefan Wahren 2019-11-14 20:35 ` Florian Fainelli 2019-11-14 20:35 ` Florian Fainelli 2019-11-15 9:02 ` Nicolas Saenz Julienne 2019-11-15 9:02 ` Nicolas Saenz Julienne 2019-11-07 9:56 ` [PATCH v3 2/2] arm64: mm: reserve CMA and crashkernel in ZONE_DMA32 Nicolas Saenz Julienne 2019-11-07 9:56 ` Nicolas Saenz Julienne 2021-03-22 18:34 ` Jon Masters 2021-03-22 18:34 ` Jon Masters 2021-03-22 18:40 ` Jon Masters 2021-03-22 18:40 ` Jon Masters 2021-03-22 18:48 ` Nicolas Saenz Julienne 2021-03-22 18:48 ` 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=20191107095611.18429-1-nsaenzjulienne@suse.de \ --to=nsaenzjulienne@suse.de \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=catalin.marinas@arm.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.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: linkBe 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.