mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Donnelly <john.p.donnelly@oracle.com>
To: Baoquan He <bhe@redhat.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>,
	Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org,
	"Eric W . Biederman" <ebiederm@xmission.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Feng Zhou <zhoufeng.zf@bytedance.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Chen Zhou <dingguo.cz@antgroup.com>,
	Dave Kleikamp <dave.kleikamp@oracle.com>,
	"samasth.norway.ananda" <samasth.norway.ananda@oracle.com>,
	John Donnelly <john.p.donnelly@oracle.com>
Subject: Re: [PATCH v3 0/2] arm64: kdump: Function supplement and performance optimization
Date: Fri, 14 Oct 2022 11:25:34 -0500	[thread overview]
Message-ID: <d0b15b1b-cf12-9da9-24f7-1fa0f4ee3757@oracle.com> (raw)
In-Reply-To: <Y0fsi4+T6k/OO0hx@MiWiFi-R3L-srv>

On 10/13/22 05:46, Baoquan He wrote:
> On 10/06/22 at 09:55am, john.p.donnelly@oracle.com wrote:
>> On 8/1/22 9:47 PM, Leizhen (ThunderTown) wrote:
> ......
>>>> Do you have plan to pick this series so that it can be taken into 5.20
>>>> rc-1~3?
>>>
>>> Hi, Catalin:
>>>     Only function reserve_crashkernel() is modified in these two patches. The core
>>> process of the arm64 architecture is not affected. I remember you suggested that
>>> arm64 and x86 share the same kdump code, so these two subfeatures are needed.
>>> Maybe we can lay the foundation first for the people who build the road. Unifying
>>> the external interfaces of kdump on arm64 and x86 does not seem to hurt.
>>>
>>>
>>>>
>>>> We have back ported the basic crashkernel=high, low, support into our
>>>> distros and have taken wide testing on arm64 servers, need this patchset
>>>> to back port for more testing.
>>>>
>>>
>> Hi ,
>>
>> What is the progress of this series ?
>>
>> Without this patch set we are seeing  larger crashkernel=896M failures on
>> Arm  with Linux-6.0.rc7.  This larger value is needed for
>> iSCSI booted systems with certain network adapters.
> 
> This change is located in arch/arm64 folder, I have pinged arm64
> maintainer to consider merging this patchset. Not sure if they are
> still thinking, or ignore this.
> 
> Hi Catalin, Will,
> 
> Ping again!
> 
> Do you have plan to accept this patchset? It's very important fo
> crashkernel setting on arm64 with a simple and default syntax.
> 
> Thanks
> Baoquan
> 
Hi,

We have pulled this into our Linux 6.0.0 QA test kernels for now. We 
would like it added too.

Thank you,

John

  reply	other threads:[~2022-10-14 16:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  9:03 Zhen Lei
2022-07-11  9:03 ` [PATCH v3 1/2] arm64: kdump: Provide default size when crashkernel=Y,low is not specified Zhen Lei
2022-08-02  8:37   ` Will Deacon
2022-08-02 10:12     ` Leizhen (ThunderTown)
2022-08-02 12:46       ` Baoquan He
2022-11-07 14:07   ` Catalin Marinas
2022-11-16 11:50     ` Leizhen (ThunderTown)
2022-11-07 17:18   ` Catalin Marinas
2022-11-08  2:47     ` Leizhen (ThunderTown)
2022-07-11  9:03 ` [PATCH v3 2/2] arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones Zhen Lei
2022-11-07 17:13   ` Catalin Marinas
2022-11-08  2:06     ` Leizhen (ThunderTown)
2022-08-01  8:20 ` [PATCH v3 0/2] arm64: kdump: Function supplement and performance optimization Baoquan He
2022-08-02  2:47   ` Leizhen (ThunderTown)
2022-10-06 14:55     ` john.p.donnelly
2022-10-13 10:46       ` Baoquan He
2022-10-14 16:25         ` John Donnelly [this message]
2022-10-14 16:29         ` Catalin Marinas
2022-10-26 19:41           ` john.p.donnelly
2022-11-15 11:58 ` Will Deacon
2022-11-15 12:18   ` Leizhen (ThunderTown)
2022-11-15 13:30     ` Catalin Marinas
2022-11-15 13:40       ` Leizhen (ThunderTown)

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=d0b15b1b-cf12-9da9-24f7-1fa0f4ee3757@oracle.com \
    --to=john.p.donnelly@oracle.com \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=dave.kleikamp@oracle.com \
    --cc=dingguo.cz@antgroup.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=samasth.norway.ananda@oracle.com \
    --cc=thunder.leizhen@huawei.com \
    --cc=vgoyal@redhat.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.org \
    --cc=zhoufeng.zf@bytedance.com \
    /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

all inboxes | Powered by JetHome®