Also, again, please make sure that [email protected] appears in the cc field of the e-mail so that the answer is forwarded to the list.
> You have two choices in this regard: > > * Either invoke PTLcalls to start/stop simulation directly from within > your program instead of calling start/stop_sim processes, or > > * Filter the YAML results with the 'user' tags to toss out anything that > happened in the kernel. > > Tyler > >> Yes I get that as I said before but it includes the simulator OS tasks >> too, >> which results in non deterministic number of cycles and simulation time. >> I >> need just the exact number of cycles which used to run the given test >> and >> number of instructions of that. How can I get that? >> >> Thanks so much >> >> >> On Mon, Sep 16, 2013 at 11:30 PM, <[email protected]> wrote: >> >>> It's in the documentation, see: >>> >>> http://marss86.org/~marss86/index.php?title=Special:Search&search=ipc >>> >>> also, both the number of cycles and instruction count are printed >>> *directly to stdout* after a simulation... >>> >>> $ ./qemu/qemu-system-x86_64 ../images/ubuntu-natty.qcow2 >>> Simulator is now waiting for a 'run' command. >>> PTLCALL type PTLCALL_ENQUEUE >>> Completed 4782000 cycles, 3194416 commits: 584328 Hz, >>> 479079 insns/sec: rip 00007f663e0bab09PTLCALL type PTLCALL_ENQUEUE >>> >>> Stopped after 4809677 cycles, 3228843 instructions and 6 seconds of sim >>> time (cycle/sec: 801612 Hz, insns/sec: 538140, insns/cyc: >>> 0.6713222114499581) >>> >>> Also, as per the last e-mail on the mailing list, please use reply-all >>> so >>> that everyone can see the answers. >>> >>> Tyler >>> >>> > I read that before, there was'nt anything useful. How do I know >>> simulator >>> > ipc and the number of instructions of a test? Do they come in stats? >>> (I >>> > couldn't find them in stats too) >>> > >>> > Thanks for your help >>> > >>> > >>> > On Sat, Sep 14, 2013 at 11:03 PM, <[email protected]> wrote: >>> > >>> >> Please read the documentation on our website... all these >>> introductory >>> >> questions are answered there. >>> >> >>> >> http://marss86.org/~marss86/index.php/Documentation >>> >> >>> >> Tyler >>> >> >>> >> > Excuse me for sending one mail twice, I couldn't see it in list >>> and >>> >> > thought >>> >> > first one didn't arrive! >>> >> > Thanks for answer by the way. May I ask where can I find >>> simulator's >>> >> > processor frequency and the number of cycles which it took to run >>> the >>> >> > test? >>> >> > Thanks again >>> >> > >>> >> > >>> >> > On Tue, Sep 10, 2013 at 1:36 AM, <[email protected]> >>> wrote: >>> >> > >>> >> >> Please do not spam the message board and repost your message >>> twice, >>> >> >> especially within a 24 hour timeframe. It is not proper message >>> board >>> >> >> etiquette. >>> >> >> >>> >> >> To answer your question: MARSS simulates processors at a fixed >>> >> frequency >>> >> >> and gives the number of cycles for which you were simulating... >>> >> >> >>> >> >> Tyler >>> >> >> >>> >> >> > Hi everyone, >>> >> >> > How can I know the benchmark execution time in MARSS? I ran FFT >>> >> >> benchmark >>> >> >> > on marss with dramsim simulator with ubuntu-natty disk image >>> which >>> >> i >>> >> >> > downloaded from >>> >> >> > here< >>> http://bertha.cs.binghamton.edu/downloads/ubuntu-natty.tar.bz2> >>> >> >> > . >>> >> >> > Thanks, >>> >> >> > Ardalan >>> >> >> > _______________________________________________ >>> >> >> > http://www.marss86.org >>> >> >> > Marss86-Devel mailing list >>> >> >> > [email protected] >>> >> >> > 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
