From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: sam.mj@au1.ibm.com
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>, linuxppc-dev@ozlabs.org
Subject: Re: [RFC PATCH] powerpc/kexec: Wait 1s for secondaries to enter OPAL
Date: Tue, 28 Jul 2015 19:58:18 +1000 [thread overview]
Message-ID: <1438077498.7562.130.camel@kernel.crashing.org> (raw)
In-Reply-To: <55B71D89.7000308@au1.ibm.com>
On Tue, 2015-07-28 at 16:13 +1000, Samuel Mendoza-Jonas wrote:
> "It sounds reasonable" was more or less the inspiration :)
> While I was going over some of the code relating to the previous kexec
> fix with Ben he pointed this out and suggested there wasn't
> much of a reason to differentiate between a crashing/non-crashing
> cpu as far as the timeout goes - if we're not 'crashing' we still
> don't want to spin forever.
>
> I'll let Ben comment on whether 1s per cpu is enough.
Well, if the scheduler doesn't give us the CPU at the point of kexec
within a second, I think we are in pretty bad shape already, don't you
think ?
I don't mind bumping the timeout of you have worries...
Cheers,
Ben.
next prev parent reply other threads:[~2015-07-28 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 5:54 [RFC PATCH] powerpc/kexec: Wait 1s for secondaries to enter OPAL Samuel Mendoza-Jonas
2015-07-27 5:56 ` Stewart Smith
2015-07-28 6:13 ` Samuel Mendoza-Jonas
2015-07-28 9:58 ` Benjamin Herrenschmidt [this message]
2015-07-29 7:24 ` Stewart Smith
2015-10-12 11:21 ` [RFC] " Michael Ellerman
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=1438077498.7562.130.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam.mj@au1.ibm.com \
--cc=stewart@linux.vnet.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 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.