From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0517C49EA4 for ; Wed, 23 Jun 2021 08:01:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 984CC61185 for ; Wed, 23 Jun 2021 08:01:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230189AbhFWIDe (ORCPT ); Wed, 23 Jun 2021 04:03:34 -0400 Received: from szxga01-in.huawei.com ([45.249.212.187]:11086 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230151AbhFWIDb (ORCPT ); Wed, 23 Jun 2021 04:03:31 -0400 Received: from dggemv704-chm.china.huawei.com (unknown [172.30.72.53]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4G8wcM22CnzZgsm; Wed, 23 Jun 2021 15:58:11 +0800 (CST) Received: from dggpemm500001.china.huawei.com (7.185.36.107) by dggemv704-chm.china.huawei.com (10.3.19.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Wed, 23 Jun 2021 16:01:12 +0800 Received: from [10.174.177.243] (10.174.177.243) by dggpemm500001.china.huawei.com (7.185.36.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Wed, 23 Jun 2021 16:01:11 +0800 Subject: Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA To: Greg KH CC: Jing Xiangfeng , Nicolas Saenz Julienne , , , , , , , , , , , , , Li Huafei References: <9bc396116372de5b538d71d8f9ae9c3259f1002e.camel@suse.de> <827b317d7f5da6e048806922098291faacdb19f9.camel@suse.de> <604597E3.5000605@huawei.com> <31cd8432-2466-555d-7617-ae48cbcd4244@huawei.com> <8b0a4f25-0803-9341-f3a4-277d16802295@huawei.com> From: Kefeng Wang Message-ID: Date: Wed, 23 Jun 2021 16:01:10 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.177.243] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To dggpemm500001.china.huawei.com (7.185.36.107) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/6/23 15:34, Greg KH wrote: > On Wed, Jun 23, 2021 at 03:25:10PM +0800, Kefeng Wang wrote: >> >> >> On 2021/6/23 15:12, Greg KH wrote: >>> On Wed, Jun 23, 2021 at 02:59:59PM +0800, Kefeng Wang wrote: >>>> Hi Greg, >>>> >>>> There are two more patches about the ZONE_DMA[32] changes, >>> >>> What ZONE_DMA changes? >> >> See the subject, [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide >> ZONE_DMA, We asked the ARM64 ZONE_DMA change backport before, link[1] Let's inline the link: https://lore.kernel.org/lkml/20210303073319.2215839-1-jingxiangfeng@huawei.com/ The following 7 patches(we asked from link) has merged into lts5.10(tag: v5.10.22) 4d7ed9a49b0c mm: Remove examples from enum zone_type comment 8eaef922e938 arm64: mm: Set ZONE_DMA size based on early IORT scan 35ec3d09ff6a arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges a9861e7fa4f8 of: unittest: Add test for of_dma_get_max_cpu_address() 18bf6e998d08 of/address: Introduce of_dma_get_max_cpu_address() 3fbe62ffbb54 arm64: mm: Move zone_dma_bits initialization into zone_sizes_init() 407b173adfac arm64: mm: Move reserve_crashkernel() into mem_init() but the patch "arm64: mm: Move reserve_crashkernel() into mem_init()" has some issue, see the following discussion from Catalin, https://lore.kernel.org/linux-devicetree/e60d643e-4879-3fc3-737d-2c145332a6d7@arm.com/ https://lore.kernel.org/linux-arm-kernel/20201119175556.18681-1-catalin.marinas@arm.com/ and yes, we met crash in lts5.10 when kexec boot due to "arm64: mm: Move reserve_crashkernel() into mem_init()" too, which could be fixed by commit 2687275a5843 "arm64: Force NO_BLOCK_MAPPINGS if crashkernel reservation is required", and the commit 791ab8b2e3db "arm64: Ignore any DMA offsets in the max_zone_phys() calculation" also about DMA set, So I only asked the two patches(both in v5.11) related ARM64 ZONE_DMA changes backported into lts5.10. > > The subject doesn't help much, sorry, what commit does this refer to? > What happened to it? Was it accepted or rejected? > >>>> especially the >>>> second one, both them need be backported, thanks. >>> >>> Backported to where? >> >> stable 5.10 > > Why? > >>>> 791ab8b2e3db - arm64: Ignore any DMA offsets in the max_zone_phys() >>>> calculation >>>> 2687275a5843 - arm64: Force NO_BLOCK_MAPPINGS if crashkernel reservation is >>>> required >>> >>> Have you tried these patches? Where do they need to be applied to? >> >> Yes, we tested it, without them, especially the second one, we will >> meet crash when using kexec boot, also there is discussion in [2] >> and [3] from Catalin. > > These [] do not seem to be links :( I could see the links is in the end, see https://lore.kernel.org/lkml/e47df0fd-0ddd-408b-2972-1b6d0a786f00@huawei.com/ > > thanks, > > greg k-h > . >