Re: [Gems-users] Thread assignment to cores

[niranjan soundararajan <niranjan83@xxxxxxxxx>]

Hello,

Thanks for the reply but the problem with these callbacks seem to be that by the time the core is stalled, a thread is already assigned to the core which I would like to avoid since it could affect the overall execution (since the thread could have been assigned to some other core).

-Niranjan

On Thu, Oct 15, 2009 at 8:32 PM, <sjafri@xxxxxxxxxx> wrote:

Not sure but check out this function:

void SimicsHypervisor::modePrivilegeToUser


Gets called by simics when a core moves from privileged mode to user(i think).
You can identify a context switch in there by comparing tids


Ali

Quoting niranjan soundararajan <niranjan83@xxxxxxxxx>:

> Hello,
>
> On a context switch (thread blocks or completes execution or timer
> interrupt), I need to disable a core for certain period. Is that possible
> without involving kernel changes?
> I know SIM_stall disables a core but is it possible to identify a context
> switch and prevent a new context from being assigned to the core .
>
> Thank you,
> Niranjan
>

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.