Hi How are you running the script ? > in "../ptlsim.log", line 2, column 10 the script converts the stat file to mcpat xml not the log file. -Furat
On Wed, Mar 27, 2013 at 5:07 PM, <[email protected]> wrote: > Hi Cesar, > > The python script was written quite some time ago (with the DVFS stuff). > We were fumbling around with the script at some time and had it working -- > perhaps the changes never got committed (or a commit broke something)? Or > maybe it's a newer version of Python that's causing errors (I'm not a > Python guy...) > > Either way, let me know if you have better luck with this script: > http//cs.binghamton.edu/~tstache1/marss/marss2mcpat.py > > Tyler > > > I could finally install MARSSx86 and is working much better than I was > > expecting (considering that I'm using Linux Mint 13 inside > VirtualBox)!!!! > > > > Now my problem is related to how convert the output to an energy XML > > profile (used by McPAT). Then I received the followin errors: > > > > 1) "Traceback (most recent call last): > > File "marss2mcpat.py", line 6, in <module> > > path = os.path.dirname(sys.argv[0]) > > NameError : name 'os' is not defined" > > * > > Solution:* moved the subsequent imports to the beginning of the file, > > before the "try/except" block. > > > > ------------------------------------------------------------------------ > > > > 2) "Parsing YAML... Malformed YAML file? Lazy error checking says: > mapping > > values are not allowed in this context > > in "../ptlsim.log", line 2, column 10 > > *Solution:* manually removing all the lines that are causing errors > > (basically, the ones that doesn't have ":" and the comments done using > > "//"). > > > > ------------------------------------------------------------------------ > > > > 3) "Traceback (most recent call last): > > File "marss2mcpat.py", line 457, in <module> > > statsDict = ReadFile(args.marss, args.cpu_mode) > > File "marss2mcpat.py", lin 37, in ReadFile > > if mode in segment['simulator']['tags']: > > KeyError: 'simulator' " > > > > *Solution:* looking for one. > > > > > > Maybe some relevant additional information: > > - the MARSSx86 code was grabbed from its GitHub, so it is the current > > version; > > - as XML file input, I've tried to use "Alpha21364.xml", > "ARM_A9_2000.xml" > > and "Xeon.xml". All those produced the same results. > > > > Any ideas of what should I do? > > > > Thanks in advance, > > Cesar. > > > > > > > > > > > > On Sat, Feb 23, 2013 at 1:17 PM, Brendan Fitzgerald > > <[email protected] > >> wrote: > > > >> Hi, > >> > >> 1. Output is written to ptlsim.log or you can specify a yamlstats file > >> to > >> get more details information. > >> 2. If you're talking about -m, it's all up to you. It sets the VM > >> memory. > >> 3. I've only used Virtualbox to compile MARSS, whenever I tried to run > >> it, > >> it was just too slow to do anything useful. As of right now, I can't > >> support a VM environment for running MARSS. > >> 4. We have McPat script in the util/ folder that you can use for power > >> estimation. > >> 5. Our website, http://marss86.org/~marss86/index.php/Home has all of > >> the > >> information you might be looking for. > >> > >> Brendan > >> > >> On Sat, Feb 23, 2013 at 3:12 AM, Cesar Augusto Marcelino dos Santos < > >> [email protected]> wrote: > >> > >>> First of all, congratulations for the MARSSx86 creators. Reading the > >>> official > >>> page and the paper about it, I've found it pretty interesting and > >>> straightforward! > >>> > >>> I am currently doing research with RTOS performance and power > >>> consumption, and > >>> by this moment, looking for power consumption simulators, and MARSSx86 > >>> looked > >>> like exactly what I wanted. > >>> > >>> I've installed in my Windows 7 64-bit a Kubuntu 12.04 LTS 64-bit under > >>> VirtualBox, and then did all the installing sequence for MARSSx86. But > >>> when I > >>> try to execute parsecROI.img (the one provided in the website), using > >>> 1024M as > >>> memory, I got an infinite loop crashing initialization, going back to > >>> GRUB > >>> counting and crashing again. > >>> Took me a while, but I got the last error messages (there's more thing > >>> displayed, but it refreshes the screen every "loop iteration"...): > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> mountall: Filesystem could not be mounted: /var/run > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1057077 > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1057077 > >>> mount: error while loading shared libraries: libblkid.so.1: cannot open > >>> shared > >>> object file: Input/output error > >>> mountall: mount /var/lock [503] terminated with status 127 > >>> mountall: Filesystem could not be mounted: /var/lock > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1057077 > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1057077 > >>> mount: error while loading shared libraries: libblkid.so.1: cannot open > >>> shared > >>> object file: Input/output error > >>> mountall: mount /lib/init/rw [504] terminated with status 127 > >>> mountall: Filesystem could not be mounted: /lib/init/rw > >>> init: mountall main process (498) terminated with status 4 > >>> Mount of root filesystem failed. > >>> A maintenance shell will now be started. > >>> CONTROL-D will terminate the shell and reboot the system. > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1174661 > >>> /dev/fd/8: 27: /sbin/sulogin: Input/output error > >>> init: mountall-shell main process (507) terminated with status 2 > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1057077 > >>> EXT3-fs error (device hda1): ext3_lookup: deleted inode referenced: > >>> 1057077 > >>> mount: error while loading shared libraries: libblkid.so.1: cannot open > >>> shared > >>> object file: Input/output error > >>> > >>> > ------------------------------------------------------------------------------ > >>> > >>> Does someone have some clue? I've tried to run also under sudo > >>> permission, with > >>> memory_size equals to 1024 and 4G too, but no results. As a last > >>> resort, > >>> I`ve > >>> tried the other 5 Ubuntu options under GRUB (when ESC is pressed), but > >>> again, > >>> nothing. > >>> > >>> Besides this, just some other questions: > >>> a) how can I redirect this output to a file? I did the "dummy way", > >>> taking > >>> screenshots and typing... > >>> b) what exactly is the "memory_size" parameter, and which values should > >>> I > >>> use? > >>> c) is it possible that the problem is that I'm running a Virtual > >>> Machine > >>> under > >>> another Virtual Machine? > >>> d) when I'm able to configure everything, how can I run a power > >>> consumption > >>> simulation (standalone application, like a "hello world", but also more > >>> complex > >>> ones, like FreeRTOS)? > >>> e) is there any tutorial on how can I run tests? Is more QEMU commands > >>> or > >>> MARSSx86 commands? What is recommended for me to read in order to > >>> understand and > >>> produce more using it? > >>> > >>> Thanks in advance. > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > > > > _______________________________________________ > 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
