There's still a problem in your script, but there was an issue in some new code that prevented you from getting a decent error message. I just pushed a patch to give you a better error message; pull it and see if it helps.
Steve On Mon, Feb 20, 2012 at 7:17 AM, Mahmood Naderan <[email protected]>wrote: > After adding that to my cmp.py, I now get this error: > > > Global frequency set at 1000000000000 ticks per second > Traceback (most recent call last): > File "<string>", line 1, in <module> > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/main.py", line > 357, in main > exec filecode in scope > File "configs/example/cmp.py", line 108, in <module> > Simulation.run(options, root, system, FutureClass) > File "/home/mahmood/gem5-ef8630054b5e/configs/common/Simulation.py", > line 245, in run > m5.instantiate(checkpoint_dir) > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/simulate.py", > line 79, in instantiate > d = root.get_config_as_dict() > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/SimObject.py", > line 939, in get_config_as_dict > d[self._children[n].get_name()] = > self._children[n].get_config_as_dict() > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/SimObject.py", > line 939, in get_config_as_dict > d[self._children[n].get_name()] = > self._children[n].get_config_as_dict() > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/params.py", line > 247, in get_config_as_dict > a.append(v.get_config_as_dict()) > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/SimObject.py", > line 939, in get_config_as_dict > d[self._children[n].get_name()] = > self._children[n].get_config_as_dict() > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/SimObject.py", > line 929, in get_config_as_dict > if type(self._values[param].value) in \ > File "/home/mahmood/gem5-ef8630054b5e/src/python/m5/util/multidict.py", > line 66, in __getitem__ > raise KeyError, e > KeyError: 'size' > > > On 2/20/12, Gabriel Michael Black <[email protected]> wrote: > > http://repo.gem5.org/gem5/file/ef8630054b5e/configs/example/se.py#l199 > > > > There's a full_system parameter when creating the simulation's Root > object. > > > > Gabe > > > > Quoting Mahmood Naderan <[email protected]>: > > > >> sorry I can not find out how se.py tells the binary to switch to SE mode > >> If I can find that, I can do the same thing in my cmp.py > >> > >> Do you know? > >> > >> On 2/20/12, Mahmood Naderan <[email protected]> wrote: > >>> it isn't compatible with previous cmp.py. > >>> I have to check and port my scripts to new one. > >>> thanks > >>> > >>> On 2/19/12, Pritha Ghoshal <[email protected]> wrote: > >>>> You can just run SE mode by building the common .opt file and then > >>>> using: > >>>> ./build/X86/gem5.opt ./configs/example/se.py. > >>>> > >>>> The se.py file also has been modified to support the change in the > >>>> binary > >>>> file.. > >>>> > >>>> Pritha > >>>> > >>>> On Sat, Feb 18, 2012 at 11:48 PM, Mahmood Naderan > >>>> <[email protected]>wrote: > >>>> > >>>>> >there is a variable set which calls the full system mode or > >>>>> >the Syscall Emulation mode. > >>>>> > >>>>> What is that then? How can I run simulation in X86_SE? > >>>>> > >>>>> On 2/18/12, Pritha Ghoshal <[email protected]> wrote: > >>>>> > Hi Mehmood, > >>>>> > > >>>>> > You have to just run this command: > >>>>> > scons build/X86/m5.debug > >>>>> > > >>>>> > The FS and SE modes have become run time usages rather than build > >>>>> > time. > >>>>> > Therefore the binary stays the same for both of them, whereas in > the > >>>>> fs.py > >>>>> > file or se.py file there is a variable set which calls the full > >>>>> > system > >>>>> mode > >>>>> > or the Syscall Emulation mode. > >>>>> > > >>>>> > Pritha > >>>>> > > >>>>> > > >>>>> > On Sat, Feb 18, 2012 at 12:36 PM, Mahmood Naderan > >>>>> > <[email protected]>wrote: > >>>>> > > >>>>> >> Hi > >>>>> >> It seems that variables in build_opt are changed in new revisions. > >>>>> >> > >>>>> >> for this command: > >>>>> >> scons build/X86_SE/m5.debug > >>>>> >> > >>>>> >> I get this error: > >>>>> >> Error: cannot find variables file > >>>>> >> /home/mahmood/gem5-ef8630054b5e/build/variables/X86_SE or default > >>>>> >> file(s) /home/mahmood/gem5-ef8630054b5e/build_opts/X86_SE > >>>>> >> > >>>>> >> comparing with previous revisions, there is no X86_SE file. > Instead > >>>>> >> there is only a file named "x86". > >>>>> >> > >>>>> >> http://repo.m5sim.org/gem5/file/ef8630054b5e/build_opts > >>>>> >> > >>>>> >> -- > >>>>> >> // Naderan *Mahmood; > >>>>> >> _______________________________________________ > >>>>> >> gem5-users mailing list > >>>>> >> [email protected] > >>>>> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > >>>>> >> > >>>>> > > >>>>> > >>>>> > >>>>> -- > >>>>> -- > >>>>> // Naderan *Mahmood; > >>>>> _______________________________________________ > >>>>> gem5-users mailing list > >>>>> [email protected] > >>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > >>>>> > >>>> > >>> > >>> > >>> -- > >>> -- > >>> // Naderan *Mahmood; > >>> > >> > >> > >> -- > >> -- > >> // Naderan *Mahmood; > >> _______________________________________________ > >> gem5-users mailing list > >> [email protected] > >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > >> > > > > _______________________________________________ > > gem5-users mailing list > > [email protected] > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > > -- > -- > // Naderan *Mahmood; > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
