There is no scheduler in SE mode.  The number of hardware thread contexts
(which is the same as the number of cores, unless you have SMT enabled in
O3) must be >= the number of software threads that get created, so each
software thread gets its own dedicated hardware context and no scheduling
is needed.

If you need a pre-emptive thread scheduler that's a good sign you really
should be running in FS mode, in my opinion.

Steve


On Sun, Jun 14, 2015 at 2:47 AM n26001482 <[email protected]>
wrote:

> Hi, all
>
> I've run multi-thread program in ARM SE mode, and it worked well. But I'm
> confused how does scheduler work in SE mode? As I know there's non-OS in
> GEM5
> SE mode and there's no scheduler in SE mode as well. So, who/what is the
> "scheduler" in charge of doing scheduling job?
>
> Thanks!!
>
> BEST
> M.Y. Lin
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to