http://triplefault.org/ 2010-09-05T07:18:07-07:00 http://triplefault.org/ http://triplefault.org/lib/images/favicon.ico text/html 2009-08-02T22:10:44-07:00 Josh http://triplefault.org/doku.php?id=josh:mm&rev=1249276244&do=diff Memory Management brain dump * <http://www.jamesmolloy.co.uk/tutorial_html/6.-Paging.html> kmalloc kmalloc() will act as in Linux text/html 2009-07-29T22:59:11-07:00 Josh http://triplefault.org/doku.php?id=josh:braindump&rev=1248933551&do=diff brain dump Dumping on Marco [14:39] ->*josh* hey, lemme run something past you.... [14:39] ->*josh* keep in mind that my kernel project is not intended to be fast. :) [14:41] ->*josh* just realized this is going to be hard to explain, so bear with me [14:42] ->*josh* im going to break up the kernel into different processes, rather than using threads. each process will have it's own memory region, but will have read access to specified pages of the calling… text/html 2009-07-29T22:20:14-07:00 Josh http://triplefault.org/doku.php?id=josh:call_page&rev=1248931214&do=diff Call Page The purpose of the call page is to provide all the required information to the kernel to appropriately call your remote function, and to provide data to the called function. Format struct call_page { u32int : shared[200]; //list of alloc'd memory pointers you wish to share (as read only) with the called function u32int : callback; //the callback function that should be called when the called function is complete } text/html 2009-07-28T15:49:54-07:00 Josh http://triplefault.org/doku.php?id=josh:kcall&rev=1248821394&do=diff kcall kcall() is the function that you would call if you need to call a remote function. Parameters kcall(function, call_page_address); 'function' is the remote function that you want to call. 'call_page_address' is the address of your call page. text/html 2009-07-28T15:39:25-07:00 Josh http://triplefault.org/doku.php?id=josh:kprocs&rev=1248820765&do=diff Kernel Processes General Kernel processes are lightweight processes that have their own memory regions. They can only read pages that they have been explicitly allowed to read and they cannot modify other processes pages. 'Modules' contain all the code for a specific purpose within the kernel. All the code within the module is in the same process scope. text/html 2009-07-27T23:08:14-07:00 Josh http://triplefault.org/doku.php?id=josh:glossary&rev=1248761294&do=diff Glossary * Kernel Modules - 'modules' in jOSh refer to a group of code that intends to perform a specific function. This could be anything from core kernel functionality to driver code. A module has it's own memory region and has no write access outside of it's own region. * Kernel Processes - jOSh does not use kernel threads. * Remote Functions - FIXME (need better name) Remote functions are functions that the kernel, or kernel modules provide to the rest of the kernel. These can not be…