From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH] Allow cpusets to be configured/built on non-SMP systems
Date: Tue, 03 Mar 2009 11:17:15 +0800 [thread overview]
Message-ID: <49ACA13B.5050106@cn.fujitsu.com> (raw)
In-Reply-To: <20090303013432.11211.18662.stgit@menage.corp.google.com>
Paul Menage 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).
>
The patch is ok for this purpose.
Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>
> Signed-off-by: Paul Menage <menage@google.com>
>
> ---
>
> init/Kconfig | 2 +-
> kernel/cpuset.c | 14 ++++++++++++++
> 2 files changed, 15 insertions(+), 1 deletions(-)
...
> +static int generate_sched_domains(struct cpumask **domains,
> + struct sched_domain_attr **attributes)
> +{
Except here should "return 0;", otherwise emit a compile warining.
> +}
next prev parent reply other threads:[~2009-03-03 3:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:36 [PATCH] Allow cpusets to be configured/built on non-SMP systems Paul Menage
[not found] ` <20090303013432.11211.18662.stgit-B63HFAS8fGlSzHKm+aFRNNkmqwFzkYv6@public.gmane.org>
2009-03-03 2:01 ` Li Zefan
2009-03-03 3:17 ` Li Zefan
2009-03-03 8:07 ` Ingo Molnar
2009-03-03 2:01 ` Li Zefan
2009-03-03 3:17 ` Li Zefan [this message]
2009-03-03 6:01 ` Paul Menage
2009-03-03 6:41 ` Paul Menage
[not found] ` <6599ad830903022201s4d2296c7u225e84a77f9f7167-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-03 6:41 ` Paul Menage
2009-03-03 8:26 ` Paul Menage
2009-03-03 8:26 ` Paul Menage
[not found] ` <6599ad830903030026w2081a72dhf3cac90346b1d806-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-03 8:42 ` Li Zefan
2009-03-03 8:42 ` Li Zefan
[not found] ` <49ACED6A.9060002-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-03-03 8:54 ` Li Zefan
2009-03-03 8:54 ` Li Zefan
[not found] ` <49ACA13B.5050106-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-03-03 6:01 ` Paul Menage
2009-03-03 8:07 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-03-03 1:36 Paul Menage
2009-03-03 23:52 Paul Menage
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=49ACA13B.5050106@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.