linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Jing Xiangfeng <jingxiangfeng@huawei.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	catalin.marinas@arm.com, will@kernel.org,
	akpm@linux-foundation.org, guohanjun@huawei.com,
	sudeep.holla@arm.com, song.bao.hua@hisilicon.com,
	ardb@kernel.org, anshuman.khandual@arm.com,
	stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Li Huafei <lihuafei1@huawei.com>
Subject: Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA
Date: Fri, 25 Jun 2021 12:19:52 +0200	[thread overview]
Message-ID: <YNWtyJaDY17829g9@kroah.com> (raw)
In-Reply-To: <f692a6e5-9e07-8b96-b7d3-213e6e3d071b@huawei.com>

On Wed, Jun 23, 2021 at 04:01:10PM +0800, Kefeng Wang wrote:
> 
> 
> 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.

Thanks, all now queued up.

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-25 10:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  7:33 [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA Jing Xiangfeng
2021-03-03  7:33 ` [PATCH stable v5.10 1/7] arm64: mm: Move reserve_crashkernel() into mem_init() Jing Xiangfeng
2021-03-07 15:25   ` Patch "arm64: mm: Move reserve_crashkernel() into mem_init()" has been added to the 5.10-stable tree gregkh
2021-03-03  7:33 ` [PATCH stable v5.10 2/7] arm64: mm: Move zone_dma_bits initialization into zone_sizes_init() Jing Xiangfeng
2021-03-07 15:25   ` Patch "arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()" has been added to the 5.10-stable tree gregkh
2021-03-03  7:33 ` [PATCH stable v5.10 3/7] of/address: Introduce of_dma_get_max_cpu_address() Jing Xiangfeng
2021-03-07 15:25   ` Patch "of/address: Introduce of_dma_get_max_cpu_address()" has been added to the 5.10-stable tree gregkh
2021-03-03  7:33 ` [PATCH stable v5.10 4/7] of: unittest: Add test for of_dma_get_max_cpu_address() Jing Xiangfeng
2021-03-07 15:25   ` Patch "of: unittest: Add test for of_dma_get_max_cpu_address()" has been added to the 5.10-stable tree gregkh
2021-03-03  7:33 ` [PATCH stable v5.10 5/7] arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges Jing Xiangfeng
2021-03-07 15:25   ` Patch "arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges" has been added to the 5.10-stable tree gregkh
2021-03-03  7:33 ` [PATCH stable v5.10 6/7] arm64: mm: Set ZONE_DMA size based on early IORT scan Jing Xiangfeng
2021-03-07 15:25   ` Patch "arm64: mm: Set ZONE_DMA size based on early IORT scan" has been added to the 5.10-stable tree gregkh
2021-03-03  7:33 ` [PATCH stable v5.10 7/7] mm: Remove examples from enum zone_type comment Jing Xiangfeng
2021-03-07 15:25   ` Patch "mm: Remove examples from enum zone_type comment" has been added to the 5.10-stable tree gregkh
2021-03-04 13:46 ` [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA Greg KH
2021-03-04 14:05   ` Nicolas Saenz Julienne
2021-03-04 14:17     ` Greg KH
2021-03-04 15:09       ` Nicolas Saenz Julienne
2021-03-07 15:24         ` Greg KH
2021-03-08  3:20           ` Jing Xiangfeng
2021-03-08  9:58             ` Greg KH
2021-05-11 12:35               ` Kefeng Wang
2021-05-12 12:06                 ` Greg KH
2021-06-23  6:59                 ` Kefeng Wang
2021-06-23  7:12                   ` Greg KH
2021-06-23  7:25                     ` Kefeng Wang
2021-06-23  7:34                       ` Greg KH
2021-06-23  8:01                         ` Kefeng Wang
2021-06-25 10:19                           ` Greg KH [this message]
2021-06-26  1:19                             ` Kefeng Wang

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=YNWtyJaDY17829g9@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=jingxiangfeng@huawei.com \
    --cc=lihuafei1@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=song.bao.hua@hisilicon.com \
    --cc=stable@vger.kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=wangkefeng.wang@huawei.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).