Dokumentation

Kernels main function.

Called after initialization of the system by kernel_init()

Note

This code will only be executed on the booting CPU (i.e., the one with ID 0).

Entry point for application processors.

Called after initialization of the system by kernel_init()

Note

Code in this function will be executed on all APs (i.e., all CPUs except ID 0)

Debug window.

Debug output using DBG like DBG << "var = " << var << endl should be displayed in window dedicated to the core it is executed on.

While this is quite easy on single core systems like OOStuBS – they only require a single TextStream object called dout – multi core systems like MPStuBS need an object array with one window per core. In the latter case direct list initialization can be used:

The debug windows in should be located right below the normal output window without any overlap and should be able to display at least 3 lines. In MPStuBS, two windows can be placed side-by-side, having 40 columns each.

As an optional extension, the distribution of the windows can be done automatically in MPStuBS (according to the actual numbers of cores) with TextStream::arrange() – in this case the standard constructor (without parameters) is sufficient.

Optional:

Automatically arrange windows with TextStream::arrange()