public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Probing for physical number of cpus.
Date: Thu, 03 Nov 2005 21:06:09 +0000	[thread overview]
Message-ID: <20051103130609.A30148@unix-os.sc.intel.com> (raw)
In-Reply-To: <200510281318.51532.Roy.Dragseth@cc.uit.no>

On Thu, Nov 03, 2005 at 12:10:34AM -0800, Roy Dragseth wrote:
> 
>    On Friday 28 October 2005 14:43, Andreas Schwab wrote:
>    > Roy Dragseth <Roy.Dragseth@cc.uit.no> writes:
>    > > Do anyone know how to figure out the physical number of cpus in an
>    ia64
>    >  >  system?   No, /proc/cpuinfo wont do because the kernel is booted
>    with
>    > > maxcpus=1.
>    >
>    >  Read  and  parse the ACPI tables off of /dev/mem, starting with the
>    address
>    > from /sys/firmware/efi/systab.
> 
>    Yikes!    Thanks  for  the  answer.   I've  been  toying  around  with
>    pmtools/acpidump
>    which  gives  me a text dump, but I'm still a bit confused (to say the
>    least).
> 

Actually even of you boot with maxcpus=1, we still create sysfs entries for
each cpus physically present in the system.

you should be able to look at /sys/devices/system/cpu/cpuX entries

if you compiled with CONFIG_HOTPLUG_CPU enabled, then you could
echo 1 > online file in the appropriate cpu directory to add more 
cpus.

Let me know if you dont see this behaviour.

Cheers,
ashok

  parent reply	other threads:[~2005-11-03 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 11:18 Probing for physical number of cpus Roy Dragseth
2005-10-28 12:43 ` Andreas Schwab
2005-11-03  8:10 ` Roy Dragseth
2005-11-03 21:06 ` Ashok Raj [this message]
2005-11-07 10:20 ` Roy Dragseth

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=20051103130609.A30148@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --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