public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Daniel Walker <dwalker@mvista.com>,
	linux-kernel@vger.kernel.org, johnstul@us.ibm.com, mingo@elte.hu,
	tglx@linutronix.de
Subject: Re: + i386-time-avoid-pit-smp-lockups.patch added to -mm tree
Date: Thu, 19 Oct 2006 16:50:25 +0200	[thread overview]
Message-ID: <200610191650.25678.ak@suse.de> (raw)
In-Reply-To: <45379031.601@yahoo.com.au>

On Thursday 19 October 2006 16:48, Nick Piggin wrote:
> Andi Kleen wrote:
> >>An SMP kernel can boot on UP hardware, in which case I think
> >>num_possible_cpus() will be 1, won't it?
> > 
> > 
> > 0 was a typo, i meant 1 for UP of course. 0 would be nonsensical.
> 
> Sure, I realised that. For a UP kernel, the test will compile away.
> 
> But Daniel seems to say there is dead code that could be compiled
> out for SMP kernels. I just don't think that is possible because the
> SMP kernel can boot a UP system where num_possible_cpus() is 1.

I thought he meant !CONFIG_SMP kernels.

-Andi

  reply	other threads:[~2006-10-19 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200610112126.k9BLQqKG002529@shell0.pdx.osdl.net>
2006-10-19 13:44 ` + i386-time-avoid-pit-smp-lockups.patch added to -mm tree Daniel Walker
2006-10-19 13:47   ` Andi Kleen
2006-10-19 13:57     ` Daniel Walker
2006-10-19 14:05       ` Andi Kleen
2006-10-19 14:50         ` Daniel Walker
2006-10-19 14:22       ` Nick Piggin
2006-10-19 14:26         ` Andi Kleen
2006-10-19 14:48           ` Nick Piggin
2006-10-19 14:50             ` Andi Kleen [this message]
2006-10-19 15:01               ` Daniel Walker
2006-10-19 18:27   ` john stultz

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=200610191650.25678.ak@suse.de \
    --to=ak@suse.de \
    --cc=dwalker@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tglx@linutronix.de \
    /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