From: Andi Kleen <ak@suse.de>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: ashok.raj@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] avoid cpu hot remove of cpus which have special RT tasks.
Date: 16 Jun 2006 11:14:57 +0200 [thread overview]
Message-ID: <p7364j1qx66.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060616162343.02c3ce62.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
>
> This is a bit pessimistic. But forecd migration of RT task which is bounded
> to the special cpu will cause unpredictable trouble, I think.
More trouble than running it on a CPU that is about to fail?
Doubtful.
It seems like a case of "never check for an error you don't know
how to handle"
-Andi
next prev parent reply other threads:[~2006-06-16 9:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 7:23 [RFC][PATCH] avoid cpu hot remove of cpus which have special RT tasks KAMEZAWA Hiroyuki
2006-06-16 9:14 ` Andi Kleen [this message]
2006-06-16 10:26 ` KAMEZAWA Hiroyuki
2006-06-16 10:36 ` Andi Kleen
2006-06-16 10:58 ` KAMEZAWA Hiroyuki
2006-06-16 11:20 ` Andi Kleen
2006-06-16 11:25 ` KAMEZAWA Hiroyuki
2006-06-17 3:46 ` Nick Piggin
2006-06-17 5:12 ` KAMEZAWA Hiroyuki
2006-06-17 7:29 ` Nick Piggin
2006-06-17 7:53 ` KAMEZAWA Hiroyuki
2006-06-17 8:48 ` Nick Piggin
2006-06-17 8:58 ` KAMEZAWA Hiroyuki
2006-06-16 16:09 ` Christoph Lameter
2006-06-16 16:46 ` KAMEZAWA Hiroyuki
2006-06-16 17:29 ` Ashok Raj
2006-06-16 23:47 ` KAMEZAWA Hiroyuki
2006-06-18 16:46 ` Pavel Machek
2006-06-19 1:12 ` KAMEZAWA Hiroyuki
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=p7364j1qx66.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=ashok.raj@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.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 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.