public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: CPU hot-remove - Handoff Processor to SAL
Date: Tue, 07 Dec 2004 15:04:14 +0000	[thread overview]
Message-ID: <20041207150414.GF10881@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20041206220159.A7973@unix-os.sc.intel.com>

On Mon, Dec 06, 2004 at 10:01:59PM -0800, Ashok Raj wrote:
> @@ -609,8 +643,10 @@ void __cpu_die(unsigned int cpu)
>  			 * TBD: Enable this when physical removal
>  			 * or when we put the processor is put in
>  			 * SAL_BOOT_RENDEZ mode
> -			 * cpu_clear(cpu, cpu_callin_map);
> +			 cpu_clear(cpu, cpu_callin_map);
> +			 printk ("Clearing cpu_callin_map\n");
>  			 */
> +			printk ("Now cpu %d is dead\n", cpu);
>  			return;
>  		}
>  		current->state = TASK_UNINTERRUPTIBLE;

Is this just a debugging printk?  I wouldn't be too happy if a customer
sees the message "Now cpu 3 is dead" in their logs.  I can almost hear
the terrified support call now ...

"I asked the machine to take the CPU offline and now it's dead!  My boss
is going to kill me!"

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-12-07 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  6:01 CPU hot-remove - Handoff Processor to SAL Ashok Raj
2004-12-07 15:04 ` Matthew Wilcox [this message]
2004-12-07 15:54 ` Matthias Fouquet-Lapar
2004-12-07 15:54 ` Ashok Raj

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=20041207150414.GF10881@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox