ZealOS does master-slave multicore instead of SMP.  Core0 is the master.    The master core's applications explicitly assign 
computational jobs to other cores and the ZealOS scheduler does not move tasks between cores.

There are multicore safe locks for file access and heap allocations, however, so ZealOS is symmetrical in some sense.  See 
::/Demo/MultiCore/LoadTest.CC.

Only tasks on Core0 can have windows, but other cores can help render them.

Each core has an Executive Task which is the father of all tasks on that core.  System is the Executive Task on Core0.

You give a job to an Executive Task with JobQueue() and get the result with JobResGet().  You spawn a task on any core with 
Spawn().

Note: You must use the LOCK asm prefix when changing shared structures in a multicore environment.  The LBts(), LBtr() and 
LBtc() insts have LOCK prefixes.    The compiler has a lock{} feature but it doesn't work well.  See 
::/Demo/MultiCore/Lock.CC.

See ::/Demo/Graphics/Transform.CC.
See ::/Kernel/MultiProc.CC.