From: Michael Ellerman <mpe@ellerman.id.au>
To: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>,
Sourabh Jain <sourabhjain@linux.ibm.com>,
linuxppc-dev@ozlabs.org
Cc: Aditya Gupta <adityag@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCH v5 1/3] powerpc: make fadump resilient with memory add/remove events
Date: Wed, 22 Nov 2023 16:17:08 +1100 [thread overview]
Message-ID: <87fs0yjrjf.fsf@mail.lhotse> (raw)
In-Reply-To: <2c0f9f9d-8cc1-4bd4-8f7f-d284140ffa43@linux.ibm.com>
Aneesh Kumar K V <aneesh.kumar@linux.ibm.com> writes:
...
>
> I am not sure whether we need to add all the complexity to enable supporting different fadump kernel
> version. Is that even a possible use case with fadump? Can't we always assume that with fadump the
> crash kernel and fadump kernel will be same version?
How sure are we of that?
Don't we go through grub when we boot into the 2nd kernel. And so
couldn't it choose to boot a different kernel, for whatever reason.
I don't think we need to support different pt_reg / cpumask sizes, but
requiring the exact same kernel version is too strict I think.
But maybe I'm wrong. Would be good to hear what distro folks think.
cheers
next prev parent reply other threads:[~2023-11-22 5:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 12:45 [PATCH v5 0/3] powerpc: make fadump resilient with memory add/remove events Sourabh Jain
2023-10-29 12:45 ` [PATCH v5 1/3] " Sourabh Jain
2023-11-09 12:14 ` Michael Ellerman
2023-11-13 6:42 ` Sourabh Jain
2023-11-15 4:44 ` Aneesh Kumar K.V
2023-11-17 4:33 ` Sourabh Jain
2023-11-17 5:31 ` Aneesh Kumar K V
2023-11-17 6:14 ` Hari Bathini
2023-11-22 5:17 ` Michael Ellerman [this message]
2023-11-22 10:35 ` Sourabh Jain
2023-11-22 12:20 ` Aneesh Kumar K V
2023-11-24 5:20 ` Sourabh Jain
2023-11-22 12:52 ` Michael Ellerman
2023-11-24 7:21 ` Sourabh Jain
2023-10-29 12:45 ` [PATCH v5 2/3] powerpc/fadump: add hotplug_ready sysfs interface Sourabh Jain
2023-10-29 12:45 ` [PATCH v5 3/3] Documentation/powerpc: update fadump implementation details Sourabh Jain
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=87fs0yjrjf.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=adityag@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=sourabhjain@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).