Hi Gavin Thanks for pointing out the TRAPTRACE mechanism. It so happens at the experiment that TJ and I want to run (we are working together) involves profiling the virtual and physical addresses prompting TLB misses through the execution of a given application. It looks like the TRAPTRACE facility allows only 32 traps to be profiled and I'm assuming that there is some sort of cap on how high this number can go up to.
Ideally, we were hoping to have a buffer (storing TLB miss info) accessible from the clock() routine that could be printed periodically to the console. We were hoping that we could access this buffer from within the TLB miss handlers to put all the TLB miss information in the buffer. However, we are unclear as to whether this is possible because the buffer initialized in the clock() routine would be allocated in virtual memory. Therefore, passing a pointer to this buffer to the TLB handler would not be helpful (since it is our understanding that the TLB handlers only access physical memory). Is there an easy way around this somehow? Thanks! Abhishek -- This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
