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]

Message-ID: <aa79d98a0805042121s1113e308obfd631581e826e0b@mail.gmail.com>
Date:	Mon, 5 May 2008 08:21:15 +0400
From:	"Cyrill Gorcunov" <gorcunov@...il.com>
To:	"Paul Jackson" <pj@....com>
Cc:	hpa@...or.com, tglx@...utronix.de, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] x86: x86-64defconfig remake

On Mon, May 5, 2008 at 3:13 AM, Paul Jackson <pj@....com> wrote:
> 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
>

Thanks Paul for feedback, will take a look today evening.
--
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/