public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 17 Mar 2023 17:30:23 +0800	[thread overview]
Message-ID: <ZBQzLxpLPcyhrDoF@MiWiFi-R3L-srv> (raw)
In-Reply-To: <cae43a11-b270-a5d6-7464-d92651c67c4a@oracle.com>

On 03/16/23 at 10:47am, Eric DeVolder wrote:
> 
> 
> On 3/16/23 09:44, Eric DeVolder wrote:
> > 
> > 
> > On 3/16/23 05:11, Baoquan He wrote:
> > > On 03/06/23 at 11:22am, Eric DeVolder wrote:
> > > ......
> > > > +static void crash_handle_hotplug_event(unsigned int hp_action, unsigned int cpu)
> > > > +{
> > > > +    /* Obtain lock while changing crash information */
> > > > +    if (kexec_trylock()) {
> > > > +
> > > > +        /* Check kdump is loaded */
> > > > +        if (kexec_crash_image) {
> > > > +            struct kimage *image = kexec_crash_image;
> > > > +
> > > > +            if (hp_action == KEXEC_CRASH_HP_ADD_CPU ||
> > > > +                hp_action == KEXEC_CRASH_HP_REMOVE_CPU)
> > > > +                pr_debug("hp_action %u, cpu %u\n", hp_action, cpu);
> > > > +            else
> > > > +                pr_debug("hp_action %u\n", hp_action);
> > > > +
> > > > +            /*
> > > > +             * When the struct kimage is allocated, the elfcorehdr_index
> > > > +             * is set to -1. Find the segment containing the elfcorehdr,
> > > > +             * if not already found. This works for both the kexec_load
> > > > +             * and kexec_file_load paths.
> > > > +             */
> > > > +            if (image->elfcorehdr_index < 0) {
> > > > +                unsigned long mem;
> > > > +                unsigned char *ptr;
> > > > +                unsigned int n;
> > > > +
> > > > +                for (n = 0; n < image->nr_segments; n++) {
> > > > +                    mem = image->segment[n].mem;
> > > > +                    ptr = kmap_local_page(pfn_to_page(mem >> PAGE_SHIFT));
> > > > +                    if (ptr) {
> > > > +                        /* The segment containing elfcorehdr */
> > > > +                        if (memcmp(ptr, ELFMAG, SELFMAG) == 0) {
> > > > +                            image->elfcorehdr_index = (int)n;
> > > > +                        }
> > > > +                        kunmap_local(ptr);
> > > > +                    }
> > > > +                }
> > > > +            }
> > > > +
> > > > +            if (image->elfcorehdr_index < 0) {
> > > > +                pr_err("unable to locate elfcorehdr segment");
> > > > +                goto out;
> > > > +            }
> > > > +
> > > > +            /* Needed in order for the segments to be updated */
> > > > +            arch_kexec_unprotect_crashkres();
> > > > +
> > > > +            /* Differentiate between normal load and hotplug update */
> > > > +            image->hp_action = hp_action;
> > > > +
> > > > +            /* Now invoke arch-specific update handler */
> > > > +            arch_crash_handle_hotplug_event(image);
> > > > +
> > > > +            /* No longer handling a hotplug event */
> > > > +            image->hp_action = KEXEC_CRASH_HP_NONE;
> > > > +            image->elfcorehdr_updated = true;
> > > 
> > > It's good to initialize the image->hp_action here, however where do
> > > you check it? Do you plan to add some check somewhere?
> > 
> > Hi Baoquan,
> > The hp_action member is initialized to 0 in do_image_alloc_init(). I've
> > mapped KEXEC_CRASH_HP_NONE onto 0 on purpose.
> > 
> > But the use of image->hp_action = KEXEC_CRASH_HP_NONE is to actually
> > delineate that a hotplug event handling has completed. You can see
> > imae->hp_action set to hp_action to capture what the triggering event
> > was, as passed into this function.
> > 
> > I will go ahead and set image->hp_action = KEXEC_CRASH_HP_NONE; explicitly
> > in do_kimage_alloc_init(), as that is done for the other crash hotplug members.
> > 
> > Thanks!
> > eric
> 
> Baoquan, as you are currently working through v19, please let me know when I
> should put out v20 with this and Sourabh's feedback.
> Thanks,
> eric

The overall serial looks good to me other than the nitpicks.


  reply	other threads:[~2023-03-17  9:31 UTC|newest]

Thread overview: 23+ 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 ` [PATCH v19 1/7] crash: move a few code bits to setup support of crash hotplug Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 2/7] crash: add generic infrastructure for crash hotplug support Eric DeVolder
2023-03-14 10:43   ` Baoquan He
2023-03-14 13:28     ` Eric DeVolder
2023-03-14 14:22       ` Baoquan He
2023-03-14 14:25         ` Eric DeVolder
2023-03-16 10:11   ` Baoquan He
2023-03-16 14:44     ` Eric DeVolder
2023-03-16 15:47       ` Eric DeVolder
2023-03-17  9:30         ` Baoquan He [this message]
2023-03-17  9:04       ` Baoquan He
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 ` [PATCH v19 4/7] crash: memory and cpu hotplug sysfs attributes Eric DeVolder
2023-03-06 16:22 ` [PATCH v19 5/7] x86/crash: add x86 crash hotplug support Eric DeVolder
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-07  8:48   ` Sourabh Jain
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-07  9:00   ` Sourabh Jain
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=ZBQzLxpLPcyhrDoF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox