From: Jesper Juhl <jesper.juhl@gmail.com>
To: Edmondo Tommasina <edmondo@eriadon.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML List <linux-kernel@vger.kernel.org>,
Discuss x86-64 <discuss@x86-64.org>
Subject: Re: Athlon 64 X2 cpuinfo oddities
Date: Mon, 9 Jan 2006 23:41:28 +0100 [thread overview]
Message-ID: <9a8748490601091441q1d6a688fr9efed06ab49dfba1@mail.gmail.com> (raw)
In-Reply-To: <200601092332.32681.edmondo@eriadon.com>
On 1/9/06, Edmondo Tommasina <edmondo@eriadon.com> wrote:
> On Monday 09-January-2006 22:10, Rafael J. Wysocki wrote:
> > Hi,
> >
>
> Same here. cpu cores is 2.
>
> Random try: Do you have CONFIG_NR_CPUS=2 in your config?
>
Yup.
$ zcat /proc/config.gz | grep NR_CPUS
CONFIG_NR_CPUS=2
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-01-09 22:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:18 Jesper Juhl
2006-01-09 20:29 ` Dave Dillow
2006-01-09 22:49 ` Jesper Juhl
2006-01-09 21:10 ` Rafael J. Wysocki
2006-01-09 22:32 ` Edmondo Tommasina
2006-01-09 22:41 ` Jesper Juhl [this message]
2006-01-09 22:49 ` Edmondo Tommasina
2006-01-10 1:49 ` Andi Kleen
2006-01-10 2:12 ` Jesper Juhl
2006-01-10 2:36 ` Andi Kleen
2006-01-10 9:29 ` Jesper Juhl
2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad
2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang
2006-01-10 20:50 ` Jeffrey Hundstad
2006-01-10 20:53 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2cpuinfooddities David Lang
2006-01-10 20:55 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities Andi Kleen
2006-01-11 0:15 ` Ken Moffat
2006-02-13 2:53 ` Brandon Low
2006-02-13 3:00 ` Alistair John Strachan
2006-02-13 9:20 ` Andi Kleen
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=9a8748490601091441q1d6a688fr9efed06ab49dfba1@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=discuss@x86-64.org \
--cc=edmondo@eriadon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®