Hi Mehmet, You have to have a kernel that has some symbols (like thread_info_size, thread_info_task, …) in it so gem5 can find these values. You probably need to add these to your kernel: http://repo.gem5.org/linux-patches/file/0ab58d9bd9a5/m5/m5struct.diff
Ali On Apr 22, 2013, at 8:11 AM, mehmet basaran <[email protected]> wrote: > Hi all, > > I am trying to get the software thread-ids per memory access in an > application. After some research I found out that this might be implemented > in ALPHA system. SO I modified the code a little bit to get the memory trace > per thread. > > in src/mem/request.hh > I included additional variables to hold thread related info. > > in src/cpu/simple/atomic.cc > in AtomicSimpleCPU::init() I tried to get thread_info and put it in request > > Linux::ThreadInfo threadInfo(tc); > ifetch_req.setThreadInfo(threadInfo.curTaskName(), > threadInfo.curTaskPID(), threadInfo.curTaskStart(), > threadInfo.curThreadInfo()); > ... > > After that I print those info in corresponding trace flags. These values are; > curTaskName() = "" > curTaskPID() = 0 > curTaskStart() = 0 > curThreadInfo() = 0 > > I think they do not provide any real info considering my application has omp > 4 threads. > > My questions are; > > 1. Where is this functionality is implemented in ALPHA mode? > 2. Any pointers on how I can get these values from kernel? > > Any help on the matter is greatly appreciated. > Regards. > > Mehmet > _______________________________________________ > 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
