Yes, I know. But the processor scheduler is implemented yet in GNU Mach code. Also the Memory Management Unit. Both components are duplicated its codes to run with a single processor and multiprocessor. May can be needed to do code fixes to repair any error, but these components exist.
Also, there is another problem with drivers, what aren't thread-safe. Then, we have to isolate these process to avoid concurrency problems El jue., 30 ago. 2018 a las 19:54, Adam Van Ymeren (<a...@vany.ca>) escribió: > Enabling multicore support in the processor is only a small part of the > problem. The OS is still in charge of deciding how to utilize those > multiple cores to run all its threads and processes. > > > > *From: *Almudena Garcia <liberamenso10...@gmail.com> > *Sent: *Thursday, August 30, 2018 1:36 PM > *To: *Richard Braun <rbr...@sceen.net>; bug-hurd@gnu.org; Joshua Branson > <jbra...@fastmail.com> > *Subject: *Re: How do I learn the Hurd stuff? > > > > But... Why we can't implement this via hardware? Configuring > multiprocessor in the CPU. > I don't know what is the problem to do this. > > > > Also, this multiprocessor support can be optional, allowing the user to > enable or disable It. > > > > > > > > > > > > El jue., 30 ago. 2018 a las 19:01, Samuel Thibault (< > samuel.thiba...@gnu.org>) escribió: > > Hello, > > Almudena Garcia, le jeu. 30 août 2018 18:58:19 +0200, a ecrit: > > Instead, It feels to use a strange implementation to do > > multithreading (not real multiprocessor) via software. > > It's not "strange", it's what all OSes do. Even with multiple > processors, OSes do that, to schedule threads on the available > processors via software. > > Samuel > > >
