From: Michael Ellerman <michael@ellerman.id.au>
To: Matt Evans <matt@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org, kexec@lists.infradead.org,
Milton Miller <miltonm@bga.com>
Subject: Re: [PATCH] kexec, ppc64: Wait for online/possible CPUs only.
Date: Wed, 09 Jun 2010 01:48:40 +1000 [thread overview]
Message-ID: <1276012120.32509.26.camel@concordia> (raw)
In-Reply-To: <4C0DF36A.3080401@ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
On Tue, 2010-06-08 at 17:38 +1000, Matt Evans wrote:
> kexec_perpare_cpus_wait() iterates i through NR_CPUS to check
> paca[i].kexec_state of each to make sure they have quiesced.
> However now we have dynamic PACA allocation, paca[NR_CPUS] is not necessarily
> valid and we overrun the array; spurious "cpu is not possible, ignoring"
> errors result. This patch iterates for_each_online_cpu so stays
> within the bounds of paca[] -- and every CPU is now 'possible'.
>
> Signed-off-by: Matt Evans <matt@ozlabs.org>
Looks good ..
Cautiously-acked-by: Michael Ellerman <michael@ellerman.id.au>
> - if (!cpu_online(i)) {
> - /* Fixme: this can be spinning in
> - * pSeries_secondary_wait with a paca
> - * waiting for it to go online.
> - */
> - printk("kexec: cpu %d hw_cpu_id %d is not"
> - " online, ignoring\n",
> - i, paca[i].hw_cpu_id);
> - break;
> - }
I don't see how the state in the Fixme could ever happen, but maybe
Milton can seeing I think he wrote it?
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-06-08 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 7:38 [PATCH] kexec, ppc64: Wait for online/possible CPUs only Matt Evans
2010-06-08 15:48 ` Michael Ellerman [this message]
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=1276012120.32509.26.camel@concordia \
--to=michael@ellerman.id.au \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@ozlabs.org \
--cc=miltonm@bga.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).