linux-kernel - Re: [RFC] x86: x86-64defconfig remake

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]

Date:	Sun, 4 May 2008 18:13:59 -0500
From:	Paul Jackson <pj@....com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	hpa@...or.com, tglx@...utronix.de, mingo@...e.hu, ak@...e.de,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] x86: x86-64defconfig remake

Cyrill wrote:
> The current x86_64_defconfig contains a number of nonexistent
> symbols.

These symbols don't exist in what context?

The one I notice:

-# CONFIG_CPUSETS is not set

certainly exists, in init/Kconfig:

    config CPUSETS
	bool "Cpuset support"
	depends on SMP && CGROUPS

and is enabled by default in some configs:

    arch/ia64/configs/sn2_defconfig
    arch/mips/configs/ip27_defconfig
    arch/mips/configs/sb1250-swarm_defconfig
    arch/powerpc/configs/cell_defconfig
    arch/powerpc/configs/ppc64_defconfig
    arch/powerpc/configspseries_defconfig

I could be tempted to enable cpusets by default in x86_64
as well, however I don't understand the tradeoffs of such
a change well enough to know if I should propose that.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/