lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080506120436.GH32591@elte.hu>
Date:	Tue, 6 May 2008 14:04:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linux Kernel <linux-kernel@...r.kernel.org>, tglx@...utronix.de,
	Mike Travis <travis@....com>,
	Arjan van de Ven <arjan@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
Subject: Re: [BUG] sysfs cpu?/topology is empty in 2.6.25 (32-bit Intel
	system)


* Vaidyanathan Srinivasan <svaidy@...ux.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ