#include "boot/startup_ap.h"
#include "machine/lapic.h"
#include "debug/output.h"
#include "device/textstream.h"
#include "machine/ioapic.h"
#include "machine/core.h"
#include "device/mouse.h"
#include "debug/gdb/stub.h"
#include "device/keyboard.h"
#include "interrupt/guard.h"
#include "user/app1/appl.h"
#include "user/app2/kappl.h"

Include dependency graph for main.cc:

Functions
int	main ()
	Kernels main function.

int	main_ap ()
	Entry point for application processors.

Constants
TextStream	kout

TextStream	dout [Core::MAX]
	Debug window.

Mouse	mouse (720, 400)

Keyboard	keyboard

static Application	apps [Core::MAX]

static KeyboardApplication	kapp

const char *	os_name = "MP" "StuBS"

Function Documentation

◆ main()

int main ( )

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).

◆ main_ap()

int main_ap ( )

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)

Variable Documentation

◆ kout

TextStream kout

◆ dout

TextStream dout[Core::MAX]

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:

TextStream dout[Core::MAX]{
   {0, 40, 17, 21},   // Debug window for core 0, like TextStream(0, 40, 17, 21)
   {40, 80, 17, 21},  // Debug window for core 1, like TextStream(40, 80, 17, 21)
   //...
 };

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()

◆ mouse

Mouse mouse(720, 400)	(	720	,
		400
	)

◆ keyboard

Keyboard keyboard

◆ apps

Application apps[Core::MAX]

static

◆ kapp

KeyboardApplication kapp