<html><body>Sorry. This mail wasn't meant for this thread.<br><aside>
---------- Původnà e-mail ----------<br>
Od: TomasSvoboda111 <TomasSvoboda111@seznam.cz><br>
Komu: Operating Systems Course <nswi004@d3s.mff.cuni.cz><br>
Datum: 16. 2. 2020 21:33:39<br>
PÅedmÄt: Re: [NSWI004] Trouble with process initiation
</aside><br><blockquote data-email="TomasSvoboda111@seznam.cz">Uz jem na to koukal a ted mam problem ze z userspaceu nemuzu zavolat syscall.<br><aside>
---------- Původnà e-mail ----------<br>
Od: Martin KoreÄek <martinkorecek23@gmail.com><br>
Komu: nswi004@d3s.mff.cuni.cz<br>
Datum: 16. 2. 2020 19:56:19<br>
PÅedmÄt: [NSWI004] Trouble with process initiation
</aside><br><blockquote data-email="martinkorecek23@gmail.com">Hello.<br><br>We are unable to initiate the userspace processes. We set the $ra and <br>$status in the process thread context and also set the SP, which seems <br>to be the problem.<br>It seems like a TLB exception is raised inside cpu_switch_ context when <br>SP should be modified, which maybe makes sense. Using the virtual SP <br>address perhaps isn't a good idea, since cpu_switch_context isn't <br>running in the correct AS yet (or so I think). Neither does using the <br>physical or kernel address.<br>Are we doing it completely wrong, or is there a simple fix to make this <br>work?<br><br>(the commit SHA is bc32b91866426118e65dcc3e8c8d788ca8005893)<br><br>Thank you in advance for any suggestions.<br>Regards,<br>Martin KoreÄek (and team sleeping_turtle)<br><br>_______________________________________________<br>NSWI004 mailing list<br>NSWI004@d3s.mff.cuni.cz<br>https://d3s.mff.cuni.cz/mailman/listinfo/nswi004<br></blockquote>_______________________________________________<br>NSWI004 mailing list<br>NSWI004@d3s.mff.cuni.cz<br>https://d3s.mff.cuni.cz/mailman/listinfo/nswi004<br></blockquote></body></html>