From: Ingo Molnar <mingo@elte.hu>
To: Paul Menage <menage@google.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] Allow cpusets to be configured/built on non-SMP systems
Date: Tue, 3 Mar 2009 09:07:34 +0100 [thread overview]
Message-ID: <20090303080734.GB11484@elte.hu> (raw)
In-Reply-To: <20090303013432.11211.18662.stgit@menage.corp.google.com>
* Paul Menage <menage@google.com> wrote:
> Allow cpusets to be configured/built on non-SMP systems
>
> Currently it's impossible to build cpusets under UML on x86-64, since
> cpusets depends on SMP and x86-64 UML doesn't support SMP.
>
> There's code in cpusets that doesn't depend on SMP. This patch
> surrounds the minimum amount of cpusets code with #ifdef CONFIG_SMP in
> order to allow cpusets to build/run on UP systems (for testing
> purposes under UML).
>
> Signed-off-by: Paul Menage <menage@google.com>
>
> ---
>
> init/Kconfig | 2 +-
> kernel/cpuset.c | 14 ++++++++++++++
> 2 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 92d2c64..3f20aa2 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -477,7 +477,7 @@ config CGROUP_DEVICE
>
> config CPUSETS
> bool "Cpuset support"
> - depends on SMP && CGROUPS
> + depends on CGROUPS
> help
> This option will let you create and manage CPUSETs which
> allow dynamically partitioning a system into sets of CPUs and
> diff --git a/kernel/cpuset.c b/kernel/cpuset.c
> index a46d693..b4d12d8 100644
> --- a/kernel/cpuset.c
> +++ b/kernel/cpuset.c
>
> @@ -517,6 +517,8 @@ static int validate_change(const struct cpuset *cur, const struct cpuset *trial)
> return 0;
> }
>
> +#ifdef CONFIG_SMP
> +
> /*
> * Helper routine for generate_sched_domains().
> * Do cpusets a, b have overlapping cpus_allowed masks?
> @@ -811,6 +813,16 @@ static void do_rebuild_sched_domains(struct work_struct *unused)
>
> put_online_cpus();
> }
> +#else
Please use:
> +#else /* !CONFIG_SMP: */
to show that it's the UP branch - even if the #ifdef itself has
scrolled off from screen already.
> +static void do_rebuild_sched_domains(struct work_struct *unused)
> +{
> +}
> +
> +static int generate_sched_domains(struct cpumask **domains,
> + struct sched_domain_attr **attributes)
> +{
> +}
> +#endif // CONFIG_SMP
Please dont use C++ comments.
Looks good otherwise. (Btw., please try to Cc: PeterZ and me to
cpusets patches in the future, especially when it affects the
scheduler.)
Ingo
next prev parent reply other threads:[~2009-03-03 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:36 Paul Menage
2009-03-03 2:01 ` Li Zefan
2009-03-03 3:17 ` Li Zefan
2009-03-03 6:01 ` Paul Menage
2009-03-03 6:41 ` Paul Menage
2009-03-03 8:26 ` Paul Menage
2009-03-03 8:42 ` Li Zefan
2009-03-03 8:54 ` Li Zefan
2009-03-03 8:07 ` Ingo Molnar [this message]
2009-03-03 23:52 Paul Menage
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=20090303080734.GB11484@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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
all inboxes | Powered by JetHome®