public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
	tglx@linutronix.de, Mike Travis <travis@sgi.com>,
	Arjan van de Ven <arjan@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: Re: [BUG] sysfs cpu?/topology is empty in 2.6.25 (32-bit Intel system)
Date: Tue, 6 May 2008 14:04:36 +0200	[thread overview]
Message-ID: <20080506120436.GH32591@elte.hu> (raw)
In-Reply-To: <20080505135215.GD5420@dirshya.in.ibm.com>


* Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> wrote:

> System topology on intel based system needs to be exported for 
> non-numa case as well.
> 
> All parts of asm-i386/topology.h has come under 
> #ifdef CONFIG_NUMA after the merge to asm-x86/topology.h
> 
> /sys/devices/system/cpu/cpu?/topology/* is populated based on 
> ENABLE_TOPO_DEFINES
> 
> The sysfs cpu topology is not being populated on my dual socket
> dual core xeon 5160 processor based (x86 32 bit) system.
> 
> CONFIG_NUMA is not set in my case yet the topology is relevant
> and useful.
> 
> irqbalance daemon application depends on topology to build the cpus 
> and package list and it fails on Fedora9 beta since the sysfs topology 
> was not being populated in the 2.6.25 kernel.
> 
> I am not sure if it was intentional to not define ENABLE_TOPO_DEFINES 
> for non-numa systems.
> 
> This fix has been tested on the above mentioned dual core, dual socket
> system.

applied, thanks Vaidyanathan.

This was certainly not intentional - i suspect nobody noticed that 
irqbalanced was working without proper topology information?

	Ingo

  parent reply	other threads:[~2008-05-06 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 13:52 [BUG] sysfs cpu?/topology is empty in 2.6.25 (32-bit Intel system) Vaidyanathan Srinivasan
2008-05-05 20:25 ` Mike Travis
2008-05-06 12:04 ` Ingo Molnar [this message]
2008-05-15 17:58   ` Vaidyanathan Srinivasan

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=20080506120436.GH32591@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=svaidy@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    /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