linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Pacaud <emmanuel.pacaud@univ-poitiers.fr>
To: Frederik Deweerdt <deweerdt@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isolcpus weirdness
Date: Thu, 23 Feb 2006 10:55:32 +0100	[thread overview]
Message-ID: <1140688532.8314.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20060222211817.GA13488@silenus.home.res>

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

Le mercredi 22 février 2006 à 22:18 +0100, Frederik Deweerdt a écrit : 
> On Wed, Feb 22, 2006 at 02:21:27PM +0100, Emmanuel Pacaud wrote:
> > What's wrong ?
> > 
> Are you able to reproduce the same behaviour after disabling HT in
> the kernel config? 

I think HT is disabled in kernel config, since I only see 2 cpus. 

In fact, I've tried to enable HT, but did'nt succeed. HT is enabled in
BIOS, but I'm not sure about exact things I must set at kernel config
level for hyperthreading. I've tried to set/unset CONFIG_SCHED_SMT, but
that changes nothing (no hyperthreading, isolated cpu is always cpu0).

Here's attached my config file.

Thanks for your interrest,

Emmanuel.

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 7447 bytes --]

  reply	other threads:[~2006-02-23  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 13:21 isolcpus weirdness Emmanuel Pacaud
2006-02-22 21:18 ` Frederik Deweerdt
2006-02-23  9:55   ` Emmanuel Pacaud [this message]
2006-02-23 10:00     ` Con Kolivas
2006-02-23 10:51       ` Emmanuel Pacaud
2006-02-23 11:37         ` Con Kolivas
2006-02-23 12:21 ` Nick Piggin
2006-02-23 13:07   ` Emmanuel Pacaud
2006-02-23 13:30     ` Nick Piggin
2006-02-23 14:03       ` Emmanuel Pacaud
2006-02-24  6:02         ` Nick Piggin
2006-02-24  7:44           ` Emmanuel Pacaud

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=1140688532.8314.10.camel@localhost.localdomain \
    --to=emmanuel.pacaud@univ-poitiers.fr \
    --cc=deweerdt@free.fr \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).