All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump
Date: Fri, 8 Apr 2022 17:32:52 +0800	[thread overview]
Message-ID: <YlABRPBEaTldZwuL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220227030717.1464-1-thunder.leizhen@huawei.com>

Hi, Lei

On 02/27/22 at 11:07am, Zhen Lei wrote:
> Changes since [v20]:
> 1. Check whether crashkernel=Y,low is incorrectly configured or not configured. Do different processing.
> 2. Share the existing description of x86. The configuration of arm64 is the same as that of x86.
> 3. Define the value of macro CRASH_ADDR_HIGH_MAX as memblock.current_limit, instead of MEMBLOCK_ALLOC_ACCESSIBLE.
> 4. To improve readability, some lightweight code adjustments have been made to reserve_craskernel(), including comments.
> 5. The defined value of DEFAULT_CRASH_KERNEL_LOW_SIZE reconsiders swiotlb, just like x86, to share documents.

5.18 rc1 is already done, do you have plan to post a new version for
reviewing?

Thanks
Baoquan



WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>,
	kexec@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
	Feng Zhou <zhoufeng.zf@bytedance.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Chen Zhou <dingguo.cz@antgroup.com>,
	John Donnelly <John.p.donnelly@oracle.com>,
	Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump
Date: Fri, 8 Apr 2022 17:32:52 +0800	[thread overview]
Message-ID: <YlABRPBEaTldZwuL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220227030717.1464-1-thunder.leizhen@huawei.com>

Hi, Lei

On 02/27/22 at 11:07am, Zhen Lei wrote:
> Changes since [v20]:
> 1. Check whether crashkernel=Y,low is incorrectly configured or not configured. Do different processing.
> 2. Share the existing description of x86. The configuration of arm64 is the same as that of x86.
> 3. Define the value of macro CRASH_ADDR_HIGH_MAX as memblock.current_limit, instead of MEMBLOCK_ALLOC_ACCESSIBLE.
> 4. To improve readability, some lightweight code adjustments have been made to reserve_craskernel(), including comments.
> 5. The defined value of DEFAULT_CRASH_KERNEL_LOW_SIZE reconsiders swiotlb, just like x86, to share documents.

5.18 rc1 is already done, do you have plan to post a new version for
reviewing?

Thanks
Baoquan


WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>,
	kexec@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
	Feng Zhou <zhoufeng.zf@bytedance.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Chen Zhou <dingguo.cz@antgroup.com>,
	John Donnelly <John.p.donnelly@oracle.com>,
	Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump
Date: Fri, 8 Apr 2022 17:32:52 +0800	[thread overview]
Message-ID: <YlABRPBEaTldZwuL@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220227030717.1464-1-thunder.leizhen@huawei.com>

Hi, Lei

On 02/27/22 at 11:07am, Zhen Lei wrote:
> Changes since [v20]:
> 1. Check whether crashkernel=Y,low is incorrectly configured or not configured. Do different processing.
> 2. Share the existing description of x86. The configuration of arm64 is the same as that of x86.
> 3. Define the value of macro CRASH_ADDR_HIGH_MAX as memblock.current_limit, instead of MEMBLOCK_ALLOC_ACCESSIBLE.
> 4. To improve readability, some lightweight code adjustments have been made to reserve_craskernel(), including comments.
> 5. The defined value of DEFAULT_CRASH_KERNEL_LOW_SIZE reconsiders swiotlb, just like x86, to share documents.

5.18 rc1 is already done, do you have plan to post a new version for
reviewing?

Thanks
Baoquan


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

  parent reply	other threads:[~2022-04-08  9:32 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27  3:07 [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2022-02-27  3:07 ` Zhen Lei
2022-02-27  3:07 ` Zhen Lei
2022-02-27  3:07 ` [PATCH v21 1/5] kdump: return -ENOENT if required cmdline option does not exist Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-03-15 11:57   ` Baoquan He
2022-03-15 11:57     ` Baoquan He
2022-03-15 11:57     ` Baoquan He
2022-03-15 12:21     ` Baoquan He
2022-03-15 12:21       ` Baoquan He
2022-03-15 12:21       ` Baoquan He
2022-03-15 13:32       ` Leizhen
2022-03-15 13:32         ` Leizhen (ThunderTown)
2022-03-15 13:32         ` Leizhen (ThunderTown)
2022-03-16  5:17         ` Baoquan He
2022-03-16  5:17           ` Baoquan He
2022-03-16  5:17           ` Baoquan He
2022-03-16  5:39   ` Baoquan He
2022-03-16  5:39     ` Baoquan He
2022-03-16  5:39     ` Baoquan He
2022-03-16  6:15     ` Leizhen
2022-03-16  6:15       ` Leizhen (ThunderTown)
2022-03-16  6:15       ` Leizhen (ThunderTown)
2022-02-27  3:07 ` [PATCH v21 2/5] arm64: Use insert_resource() to simplify code Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-02-27  3:07 ` [PATCH v21 3/5] arm64: kdump: reimplement crashkernel=X Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-03-16 12:11   ` Baoquan He
2022-03-16 12:11     ` Baoquan He
2022-03-16 12:11     ` Baoquan He
2022-03-16 13:11     ` Leizhen
2022-03-16 13:11       ` Leizhen (ThunderTown)
2022-03-16 13:11       ` Leizhen (ThunderTown)
2022-03-17  2:36       ` Baoquan He
2022-03-17  2:36         ` Baoquan He
2022-03-17  2:36         ` Baoquan He
2022-03-17  3:19         ` Leizhen
2022-03-17  3:19           ` Leizhen (ThunderTown)
2022-03-17  3:19           ` Leizhen (ThunderTown)
2022-03-17  3:47           ` Baoquan He
2022-03-17  3:47             ` Baoquan He
2022-03-17  3:47             ` Baoquan He
2022-03-17  7:30             ` Leizhen
2022-03-17  7:30               ` Leizhen (ThunderTown)
2022-03-17  7:30               ` Leizhen (ThunderTown)
2022-03-17  2:38   ` Baoquan He
2022-03-17  2:38     ` Baoquan He
2022-03-17  2:38     ` Baoquan He
2022-03-17  3:23     ` Leizhen
2022-03-17  3:23       ` Leizhen (ThunderTown)
2022-03-17  3:23       ` Leizhen (ThunderTown)
2022-03-21 13:29   ` John Donnelly
2022-03-21 13:29     ` John Donnelly
2022-03-21 13:29     ` John Donnelly
2022-03-21 14:09     ` Dave Kleikamp
2022-03-21 14:09       ` Dave Kleikamp
2022-03-21 14:09       ` Dave Kleikamp
2022-03-22  1:58     ` Leizhen
2022-03-22  1:58       ` Leizhen (ThunderTown)
2022-03-22  1:58       ` Leizhen (ThunderTown)
2022-02-27  3:07 ` [PATCH v21 4/5] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-02-27  3:07   ` [PATCH v21 4/5] of: fdt: Add memory for devices by DT property "linux,usable-memory-range" Zhen Lei
2022-02-27  3:07 ` [PATCH v21 5/5] docs: kdump: Update the crashkernel description for arm64 Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-02-27  3:07   ` Zhen Lei
2022-03-15 11:59   ` Baoquan He
2022-03-15 11:59     ` Baoquan He
2022-03-15 11:59     ` Baoquan He
2022-04-08  9:32 ` Baoquan He [this message]
2022-04-08  9:32   ` [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump Baoquan He
2022-04-08  9:32   ` Baoquan He
2022-04-08  9:47   ` Leizhen
2022-04-08  9:47     ` Leizhen (ThunderTown)
2022-04-08  9:47     ` Leizhen (ThunderTown)
2022-04-11  2:56     ` Baoquan He
2022-04-11  2:56       ` Baoquan He
2022-04-11  2:56       ` Baoquan He

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=YlABRPBEaTldZwuL@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=kexec@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: 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.