From: Baoquan He <bhe@redhat.com>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, ebiederm@xmission.com,
dyoung@redhat.com, vgoyal@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, nramas@linux.microsoft.com,
thomas.lendacky@amd.com, robh@kernel.org, efault@gmx.de,
rppt@kernel.org, david@redhat.com, sourabhjain@linux.ibm.com,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com
Subject: Re: [PATCH v19 2/7] crash: add generic infrastructure for crash hotplug support
Date: Tue, 14 Mar 2023 22:22:54 +0800 [thread overview]
Message-ID: <ZBCDPuTdjMY+7VrG@MiWiFi-R3L-srv> (raw)
In-Reply-To: <2fd31764-b341-638a-f70e-43dc0d5b0092@oracle.com>
On 03/14/23 at 08:28am, Eric DeVolder wrote:
......
> > > +static int crash_memhp_notifier(struct notifier_block *nb, unsigned long val, void *v)
> > > +{
> > > + switch (val) {
> > > + case MEM_ONLINE:
> > > + crash_handle_hotplug_event(KEXEC_CRASH_HP_ADD_MEMORY,
> > > + KEXEC_CRASH_HP_INVALID_CPU);
> > > + break;
> > > +
> > > + case MEM_OFFLINE:
> > > + crash_handle_hotplug_event(KEXEC_CRASH_HP_REMOVE_MEMORY,
> > > + KEXEC_CRASH_HP_INVALID_CPU);
> > > + break;
> > > + }
> > > + return NOTIFY_OK;
> > > +}
> > > +
> > > +static struct notifier_block crash_memhp_nb = {
> > > + .notifier_call = crash_memhp_notifier,
> > > + .priority = 0
> > > +};
> > > +
> >
> > Because for_each_possible_cpu() is taken in
> > crash_prepare_elf64_headers(), x86 doesn't need to respond to cpu
> > hotplug or doesn't do anything with this patchset. This cpu part in
> > infrastructure is only for the later powerpc usage, right?
>
> That is true, yes.
Given this patchset is aimed at crash hotplug on x86, while obviously it
does't need to have the cpu hotplug support on x86 since the
for_each_possible_cpu() adjustment. People looking into this may be
confused if they don't follow the discussion thread of v18. Do we need
to mention this in cover letter or somewhere else? I could miss that
though it is has been told, please ignore this if yes.
_______________________________________________
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: Eric DeVolder <eric.devolder@oracle.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, ebiederm@xmission.com,
dyoung@redhat.com, vgoyal@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, nramas@linux.microsoft.com,
thomas.lendacky@amd.com, robh@kernel.org, efault@gmx.de,
rppt@kernel.org, david@redhat.com, sourabhjain@linux.ibm.com,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com
Subject: Re: [PATCH v19 2/7] crash: add generic infrastructure for crash hotplug support
Date: Tue, 14 Mar 2023 22:22:54 +0800 [thread overview]
Message-ID: <ZBCDPuTdjMY+7VrG@MiWiFi-R3L-srv> (raw)
In-Reply-To: <2fd31764-b341-638a-f70e-43dc0d5b0092@oracle.com>
On 03/14/23 at 08:28am, Eric DeVolder wrote:
......
> > > +static int crash_memhp_notifier(struct notifier_block *nb, unsigned long val, void *v)
> > > +{
> > > + switch (val) {
> > > + case MEM_ONLINE:
> > > + crash_handle_hotplug_event(KEXEC_CRASH_HP_ADD_MEMORY,
> > > + KEXEC_CRASH_HP_INVALID_CPU);
> > > + break;
> > > +
> > > + case MEM_OFFLINE:
> > > + crash_handle_hotplug_event(KEXEC_CRASH_HP_REMOVE_MEMORY,
> > > + KEXEC_CRASH_HP_INVALID_CPU);
> > > + break;
> > > + }
> > > + return NOTIFY_OK;
> > > +}
> > > +
> > > +static struct notifier_block crash_memhp_nb = {
> > > + .notifier_call = crash_memhp_notifier,
> > > + .priority = 0
> > > +};
> > > +
> >
> > Because for_each_possible_cpu() is taken in
> > crash_prepare_elf64_headers(), x86 doesn't need to respond to cpu
> > hotplug or doesn't do anything with this patchset. This cpu part in
> > infrastructure is only for the later powerpc usage, right?
>
> That is true, yes.
Given this patchset is aimed at crash hotplug on x86, while obviously it
does't need to have the cpu hotplug support on x86 since the
for_each_possible_cpu() adjustment. People looking into this may be
confused if they don't follow the discussion thread of v18. Do we need
to mention this in cover letter or somewhere else? I could miss that
though it is has been told, please ignore this if yes.
next prev parent reply other threads:[~2023-03-14 14:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 16:22 [PATCH v19 0/7] crash: Kernel handling of CPU and memory hot un/plug Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 1/7] crash: move a few code bits to setup support of crash hotplug Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 2/7] crash: add generic infrastructure for crash hotplug support Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-14 10:43 ` Baoquan He
2023-03-14 10:43 ` Baoquan He
2023-03-14 13:28 ` Eric DeVolder
2023-03-14 13:28 ` Eric DeVolder
2023-03-14 14:22 ` Baoquan He [this message]
2023-03-14 14:22 ` Baoquan He
2023-03-14 14:25 ` Eric DeVolder
2023-03-14 14:25 ` Eric DeVolder
2023-03-16 10:11 ` Baoquan He
2023-03-16 10:11 ` Baoquan He
2023-03-16 14:44 ` Eric DeVolder
2023-03-16 14:44 ` Eric DeVolder
2023-03-16 15:47 ` Eric DeVolder
2023-03-16 15:47 ` Eric DeVolder
2023-03-17 9:30 ` Baoquan He
2023-03-17 9:30 ` Baoquan He
2023-03-17 9:04 ` Baoquan He
2023-03-17 9:04 ` Baoquan He
2023-03-17 18:13 ` Eric DeVolder
2023-03-17 18:13 ` Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 3/7] kexec: exclude elfcorehdr from the segment digest Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 4/7] crash: memory and cpu hotplug sysfs attributes Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 5/7] x86/crash: add x86 crash hotplug support Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-08 3:08 ` Sourabh Jain
2023-03-08 3:08 ` Sourabh Jain
2023-03-06 16:22 ` [PATCH v19 6/7] crash: change crash_prepare_elf64_headers() to for_each_possible_cpu() Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-07 8:48 ` Sourabh Jain
2023-03-07 8:48 ` Sourabh Jain
2023-03-17 19:12 ` Eric DeVolder
2023-03-17 19:12 ` Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 7/7] x86/crash: optimize cpu changes Eric DeVolder
2023-03-06 16:22 ` Eric DeVolder
2023-03-07 9:00 ` Sourabh Jain
2023-03-07 9:00 ` Sourabh Jain
2023-03-17 18:42 ` Eric DeVolder
2023-03-17 18:42 ` Eric DeVolder
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=ZBCDPuTdjMY+7VrG@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=efault@gmx.de \
--cc=eric.devolder@oracle.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nramas@linux.microsoft.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=sourabhjain@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vgoyal@redhat.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.