[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4846F0DE.1070708@qualcomm.com>
Date: Wed, 04 Jun 2008 12:45:34 -0700
From: Max Krasnyansky <maxk@...lcomm.com>
To: Paul Jackson <pj@....com>
CC: andi@...stfloor.org, ioe-lkml@...eria.de, sivanich@....com,
a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org,
kernel@...ivas.org, dfults@....com, devik@....cz, dino@...ibm.com,
emmanuel.pacaud@...v-poitiers.fr, deweerdt@...e.fr, mingo@...e.hu,
colpatch@...ibm.com, nickpiggin@...oo.com.au, rostedt@...dmis.org,
oleg@...sign.ru, paulmck@...ibm.com, menage@...gle.com,
rddunlap@...l.org, suresh.b.siddha@...el.com, tglx@...utronix.de
Subject: Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may
have realtime uses)
Paul Jackson wrote:
>> btw Are you guys using some kind of castrated, statically linked shell to run
>> that script ?
>
> It (that init= program) is not a script. It is its own
> castrated, statically linked special purpose binary.
> Once it has done its duty setting up cpusets, it then
> exec's the normal init, confined to the cpuset configured
> for it.
Got it.
Max
--
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/
Powered by blists - more mailing lists