From: Pavel Machek <pavel@ucw.cz>
To: Nathan Lynch <nathanl@austin.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] ppc64 gives up too quickly on hotplugged cpu
Date: Thu, 10 Jun 2004 14:03:51 +0200 [thread overview]
Message-ID: <20040610120350.GC4507@openzaurus.ucw.cz> (raw)
In-Reply-To: <40BE5B6E.7060109@austin.ibm.com>
Hi!
> On some systems it can take a hotplugged cpu much longer to come up
> than it would at boot. If the cpu comes up after we've given up on
> it, it tends to die in its first attempt to kmem_cache_alloc
> (uninitialized percpu data, I imagine).
Should not CPU check if system given up on it, and go to infinite
loop if it did to prevent data corruption?
Ouch and please inline patches.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
prev parent reply other threads:[~2004-06-10 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 22:57 [PATCH] ppc64 gives up too quickly on hotplugged cpu Nathan Lynch
2004-06-10 12:03 ` Pavel Machek [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=20040610120350.GC4507@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox