From: "Cyrill Gorcunov" <gorcunov@gmail.com>
To: "Paul Jackson" <pj@sgi.com>
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] x86: x86-64defconfig remake
Date: Mon, 5 May 2008 08:21:15 +0400 [thread overview]
Message-ID: <aa79d98a0805042121s1113e308obfd631581e826e0b@mail.gmail.com> (raw)
In-Reply-To: <20080504181359.a39d766b.pj@sgi.com>
On Mon, May 5, 2008 at 3:13 AM, Paul Jackson <pj@sgi.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@sgi.com> 1.940.382.4214
>
Thanks Paul for feedback, will take a look today evening.
next prev parent reply other threads:[~2008-05-05 4:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 15:57 Cyrill Gorcunov
2008-05-04 18:06 ` Ingo Molnar
2008-05-04 18:36 ` Cyrill Gorcunov
2008-05-04 23:13 ` Paul Jackson
2008-05-05 4:21 ` Cyrill Gorcunov [this message]
2008-05-05 7:03 ` Ingo Molnar
2008-05-05 7:33 ` Paul Jackson
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=aa79d98a0805042121s1113e308obfd631581e826e0b@mail.gmail.com \
--to=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®