On Fri, Aug 10, 2012 at 7:11 AM, snataraj <[email protected]> wrote:
> I saw in marss paper that MARSS uses QEMUs opcode helper function to > emulate complicated opcodes like fxsaver, fxrstor, syscall and sysret. > 1. When they are emulated how do we get the statisitcs for the system > calls as the system call is executed on the native machine? > System calls are executed in simulation mode, they are not executed by native machine. To see how many times 'syscall' is called you can check 'syscall' counter in statistics. To check value of 'syscall' use following command: $ util/mstats.py -y --yaml-out -t total -n "base_machine::ooo_*::thread0::assists::syscall" YOUR_STATS_FILE 2. In general how are the kernal statistics obtained? > > Marss simulates all kernel activities just like user level applications. So all kernel statistics are collected via simulating kernel level instructions. Also Marss has statistics framework that captures separate statistics for user and kernel level executions. In each stats files there are 3 instance of stats, one for user level, one for kernel and third is total (sum of user and kernel). Look into 'tags' to find which type of stats it is. - Avadh > -- > Surya Narayanan, E301 - 12, Inria Rennes - Bretagne Atlantique Research > Centre Campus universitaire de Beaulieu 35042 Rennes Cedex > > ______________________________**_________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected].**edu <[email protected]> > https://www.cs.binghamton.edu/**mailman/listinfo/marss86-devel<https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel> >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
