From: Trent Piepho <tpiepho@freescale.com>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: __cpu_up vs. start_secondary race?
Date: Tue, 2 Dec 2008 20:14:45 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0812022009220.10176@t2.domain.actdsltmp> (raw)
In-Reply-To: <20081203021624.GE6829@localdomain>
On Tue, 2 Dec 2008, Nathan Lynch wrote:
> Apart from barriers (or lack thereof), the fact that __cpu_up gives up
> after a more-or-less arbitrary period seems... well, arbitrary. If we
> get to "Processor X is stuck" then something is seriously wrong:
> there's either a kernel bug or a platform issue, and the CPU just
> kicked is in an unknown state. Polling indefinitely seems safer, no?
I recently fixed a bug that did this. There was a bug in how the secondary
CPU's memory was mapped (in some non-mailine code, not fixed). It was nice
to get the warning and have the kernel not hang. On embedded systems with
only network access and no persistent storage for system logs, a kernel
hang is a lot more a pain.
next prev parent reply other threads:[~2008-12-03 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 21:30 __cpu_up vs. start_secondary race? Nathan Lynch
2008-12-01 22:08 ` Benjamin Herrenschmidt
2008-12-03 2:16 ` Nathan Lynch
2008-12-03 4:14 ` Trent Piepho [this message]
2008-12-03 4:52 ` Benjamin Herrenschmidt
2008-12-03 5:20 ` Nathan Lynch
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=Pine.LNX.4.64.0812022009220.10176@t2.domain.actdsltmp \
--to=tpiepho@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.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