From: Baoquan He <bhe@redhat.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: Petr Tesarik <petr@tesarici.cz>,
Hari Bathini <hbathini@linux.ibm.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org
Subject: Re: [PATCH v2] Document/kexec: Generalize crash hotplug description
Date: Tue, 13 Aug 2024 17:17:04 +0800 [thread overview]
Message-ID: <ZrskkDuMlQu+uBN4@MiWiFi-R3L-srv> (raw)
In-Reply-To: <4cbbf314-5134-4a1a-8a4d-f6f8c09104d3@linux.ibm.com>
On 08/13/24 at 10:58am, Sourabh Jain wrote:
> Hello Baoquan,
>
> On 13/08/24 10:34, Baoquan He wrote:
> > On 08/12/24 at 09:46am, Sourabh Jain wrote:
> > ......
> > > ---
> > >
> > > Changelog:
> > >
> > > Since v1: https://lore.kernel.org/all/20240805050829.297171-1-sourabhjain@linux.ibm.com/
> > > - Update crash_hotplug sysfs document as suggested by Petr T
> > > - Update an error message in crash_handle_hotplug_event and
> > > crash_check_hotplug_support function.
> > >
> > > ---
> > ......
> > > diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> > > index 63cf89393c6e..c1048893f4b6 100644
> > > --- a/kernel/crash_core.c
> > > +++ b/kernel/crash_core.c
> > > @@ -505,7 +505,7 @@ int crash_check_hotplug_support(void)
> > > crash_hotplug_lock();
> > > /* Obtain lock while reading crash information */
> > > if (!kexec_trylock()) {
> > > - pr_info("kexec_trylock() failed, elfcorehdr may be inaccurate\n");
> > > + pr_info("kexec_trylock() failed, kdump image may be inaccurate\n");
> > Wondering why this need be updated.
>
> In some architectures, additional kexec segments become obsolete during a
> hotplug event,
> so simply calling out the `elfcorehdr may be inaccurate` may not be
> sufficient.
> Therefore, it has been generalized with the kdump image.
OK, I forgot the case in ppc, makes sense to me, thx.
Acked-by: Baoquan He <bhe@redhat.com>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: Petr Tesarik <petr@tesarici.cz>,
Hari Bathini <hbathini@linux.ibm.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org
Subject: Re: [PATCH v2] Document/kexec: Generalize crash hotplug description
Date: Tue, 13 Aug 2024 17:17:04 +0800 [thread overview]
Message-ID: <ZrskkDuMlQu+uBN4@MiWiFi-R3L-srv> (raw)
In-Reply-To: <4cbbf314-5134-4a1a-8a4d-f6f8c09104d3@linux.ibm.com>
On 08/13/24 at 10:58am, Sourabh Jain wrote:
> Hello Baoquan,
>
> On 13/08/24 10:34, Baoquan He wrote:
> > On 08/12/24 at 09:46am, Sourabh Jain wrote:
> > ......
> > > ---
> > >
> > > Changelog:
> > >
> > > Since v1: https://lore.kernel.org/all/20240805050829.297171-1-sourabhjain@linux.ibm.com/
> > > - Update crash_hotplug sysfs document as suggested by Petr T
> > > - Update an error message in crash_handle_hotplug_event and
> > > crash_check_hotplug_support function.
> > >
> > > ---
> > ......
> > > diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> > > index 63cf89393c6e..c1048893f4b6 100644
> > > --- a/kernel/crash_core.c
> > > +++ b/kernel/crash_core.c
> > > @@ -505,7 +505,7 @@ int crash_check_hotplug_support(void)
> > > crash_hotplug_lock();
> > > /* Obtain lock while reading crash information */
> > > if (!kexec_trylock()) {
> > > - pr_info("kexec_trylock() failed, elfcorehdr may be inaccurate\n");
> > > + pr_info("kexec_trylock() failed, kdump image may be inaccurate\n");
> > Wondering why this need be updated.
>
> In some architectures, additional kexec segments become obsolete during a
> hotplug event,
> so simply calling out the `elfcorehdr may be inaccurate` may not be
> sufficient.
> Therefore, it has been generalized with the kdump image.
OK, I forgot the case in ppc, makes sense to me, thx.
Acked-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2024-08-13 9:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 4:16 [PATCH v2] Document/kexec: Generalize crash hotplug description Sourabh Jain
2024-08-12 4:16 ` Sourabh Jain
2024-08-12 4:16 ` Sourabh Jain
2024-08-12 5:41 ` Petr Tesarik
2024-08-12 5:41 ` Petr Tesarik
2024-08-12 5:41 ` Petr Tesarik
2024-08-12 5:45 ` Sourabh Jain
2024-08-12 5:45 ` Sourabh Jain
2024-08-12 5:45 ` Sourabh Jain
2024-08-13 5:04 ` Baoquan He
2024-08-13 5:04 ` Baoquan He
2024-08-13 5:28 ` Sourabh Jain
2024-08-13 5:28 ` Sourabh Jain
2024-08-13 9:17 ` Baoquan He [this message]
2024-08-13 9:17 ` Baoquan He
2024-08-13 9:25 ` Sourabh Jain
2024-08-13 9:25 ` Sourabh Jain
2024-08-19 4:11 ` Sourabh Jain
2024-08-19 4:11 ` Sourabh Jain
2024-08-19 9:36 ` Baoquan He
2024-08-19 9:36 ` 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=ZrskkDuMlQu+uBN4@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=petr@tesarici.cz \
--cc=sourabhjain@linux.ibm.com \
--cc=x86@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 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.