Any additional advice on being able to this is appreciated. Basically I want to have M5 be able to distinguish between threads not CPU. Since in PARSEC benchmarks, threads tend to move around between CPUs.
On Sat, May 22, 2010 at 9:57 AM, Steve Reinhardt <[email protected]> wrote: > There's nothing built-in for this that I know of. The issue is that > you're trying to detect an OS event... you could hook some action that > the OS takes only when scheduling a new thread, like perhaps updating > the page table base pointer or writing to the uniq register (via the > wruniq instruction). Someone like Nate or Ali who's done more > hands-on low-level Alpha Linux work could provide better details I'm > sure. > > Steve > > On Tue, May 18, 2010 at 9:15 PM, ef <[email protected]> wrote: > > Hello, > > > > I was wondering if there is a way for m5 (not glibc or the kernel) to > signal > > when a new thread is on a cpu. I have some benchmarks that create new > > threads in the middle of execution, and I would like to see output on > them > > being pinned to processors (I have more threads than processors, FS > MODE). I > > looked through and tested trace flags and I couldnt find anything. Is > there > > such flag? > > > > If not anyone know where I should implement a DPRINTF in m5 to do this? > > > > Thanks, > > EF > > > > _______________________________________________ > > m5-users mailing list > > [email protected] > > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
