OK, I found the bug. It was my fault while coding. // Naderan *Mahmood;
From: Volos Stavros <[email protected]> To: Mahmood Naderan <[email protected]>; simflex <[email protected]> Sent: Monday, June 27, 2011 1:42 PM Subject: RE: CPU[0] idle_thread_t point at paddr: p:000000000 Dear Mahmood, Whitebox's role is to identify the memory addresses in Solaris kernel that give the ID of the thread running on each cpu. There are many values in the WhiteBox component that are hardcoded for Solaris 8. However this does not affect the execution, so it's safe. Regards, -Stavros. ________________________________________ From: Mahmood Naderan [[email protected]] Sent: Sunday, June 26, 2011 5:59 PM To: simflex Subject: CPU[0] idle_thread_t point at paddr: p:000000000 Hi, I don't why what is happen that during debug, all VirtualMemoryAddress variables and "aPC" are zero? The output of UP.Trace contains 35 <mai_api.cpp:273> {0}- Searching 1 cpus. 36 <mai_api.cpp:277> {0}- Processor 0: cpu0 - CPU 0 37 <mai_api.cpp:296> {0}- Found CPU: '' - 0 38 <mai_api.cpp:313> {0}- Found 1 Flexus CPUs and 0 Client CPUs in 0 VMs 39 <mai_api.cpp:352> {0}- VMS per row = 1, CPVM = 1, NVMR = 1, NumRow = 1 40 <mai_api.cpp:379> {0}- theProcMap[0] = (0, 0) (abs_index = 0) 41 <mai_api.cpp:384> {0}- Finished creating Processor Mapper. 42 <flexus.cpp:272> {0}- Timestamp: 2011-Jun-26 19:58:01 And the output of UP.OoO contains: 73 <ValueTracker.hpp:251> {6}- Done registering DMA tracker 74 <WhiteBoxImpl.cpp:178> {7}- initializing idle_thread_t's, num procs=1 sys width=1 75 <WhiteBoxImpl.cpp:195> {7}- CPU[0] idle_thread_t point at paddr: p:000000000 76 <mai_api.cpp:93> {7}- CPU[0] Registering for interrupts 77 <microArch.cpp:365> {10000}- Timestamp: 2011-Jun-26 20:16:12 What does CPU[0] idle_thread_t point at paddr: p:000000000 mean? is it safe? // Naderan *Mahmood;
