Skip to content

Conversation

sigsegv4
Copy link

tfork, PCP und CAS implementiert.
Bitte um Rueckmeldung ob die treiberstack implementation so passt.

mit make cas wird der test mit cas aufgerufen
mit make ncas wird der test ohne cas aufgerufen (Hat noch einen bug beendet nicht)

in der file testPCP_cas.c ist der Testcode fuer cas ,
in der file testPCP_noCAS.c ist der Testcode ohne cas hypercall.

Christian Kawalar and others added 29 commits December 12, 2015 16:25
…s, that store our kernel Args Address, we can write our params now directly into the memory
…ed p1.mips32, createcontext and deletecontext, and execute and exit the processes right, note: we have some things hardcoded, we fix them up in the next few commits, try the OS with <make all>
mc_switchAfterMInstructions, code cleanup, still self-compiling but not
self-running. ( Due the nature of our implementation that the first
loaded binary must be the kernel.mips32!)
…letecontext, as for now i dont see why we would ned a hypercall for that so no flushPageInContext hyperall
Write test file to show difference with the consumer producer problem,
without CAS and with CAS. To run the test: make cas, make ncas
…mutex variable now to ensure that only one thread at a time can write / read the stack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants