[Bugme-new] [Bug 6733] New: init task run on wrong cpu when using isolcpus

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=6733

           Summary: init task run on wrong cpu when using isolcpus
    Kernel Version: 2.6.17-rc3
            Status: NEW
          Severity: normal
             Owner: rlove at rlove.org
         Submitter: emmanuel.pacaud at lapp.in2p3.fr


Distribution: Scientific linux 4.2
Hardware Environment: Dual xeon 3.2GHz
Problem Description:

When using isolcpus kernel parameter, init task may runs on one of the isolated
cpus, which is not someting we want. For example, on my test platform, init task
always run on last cpu, whatever isolcpus value is.

Since isolated cpus are isolated from scheduler task balancing, all processes
will run on only one cpu. 

Also, one of the use of isolcpus parameter is for isolate a realtime task from
all normal tasks. For example, on my system, if I set isolcpus=3, I expect to
have all normal tasks on cpu 0, 1 and 2, which let me run a real time task on cpu 3.

Good behaviour would be to launch init task on one of the non isolated cpus.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.