public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-rc3 -- SMP alternatives: switching to UP code
Date: Wed, 10 May 2006 11:28:42 +0200	[thread overview]
Message-ID: <4461B24A.7050805@suse.de> (raw)
In-Reply-To: <4461341B.7050602@keyaccess.nl>

Rene Herman wrote:
> Hi list.
> 
> I just noticed this in the 2.6.17-rc3 dmesg:
> 
> ===
> Checking 'hlt' instruction... OK.
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 0k freed
> ACPI: setting ELCR to 0400 (from 1608)
> ===
> 
> Should I be seeing this "SMP alternatives" thing on a !CONFIG_SMP
> kernel? It does say 0k, but something is apparently being done at
> runtime still. Why?

The UP kernel has empty alternatives tables (as you've noticed), thus
the code doesn't do anything.  Nevertheless it probably makes sense to
add a few #ifdef CONFIG_SMP lines to avoid confusing people and safe a
few bytes ...

cheers,

  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>
Erst mal heiraten, ein, zwei Kinder, und wenn alles läuft
geh' ich nach drei Jahren mit der Familie an die Börse.
http://www.suse.de/~kraxel/julika-dora.jpeg

  parent reply	other threads:[~2006-05-10  9:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  0:30 2.6.17-rc3 -- SMP alternatives: switching to UP code Rene Herman
2006-05-10  1:55 ` Chase Venters
2006-05-10  9:28 ` Gerd Hoffmann [this message]
2006-05-10 11:41   ` Rene Herman
2006-05-11 12:13     ` [patch] SMP alternatives: skip with UP kernels Gerd Hoffmann
2006-05-11 21:07       ` Rene Herman
2006-05-12 11:41         ` Gerd Hoffmann
2006-05-15 21:41           ` Rene Herman

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=4461B24A.7050805@suse.de \
    --to=kraxel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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