The first is of course easy. The second is a bit harder. Adding types to parameters should be easy. The problem is that the definition of a tick can be changed, and that change happens after the command line arguments are parsed. I wonder if we should remove this flexibility or make it a compile time thing. We could also force the definition of a tick to be done in a command line option (which can be configured via the .m5/options.py) stuff or via an environment variable. Either that, or you'd have to delay the creation of the progress event until startup happens.
Nate On Thu, Oct 9, 2008 at 8:56 AM, Steve Reinhardt <[EMAIL PROTECTED]> wrote: > Seems like it would be useful to have a --progress=N command-line option for > this... I thought there used to be one. > > This would be even more useful with the ability to run command-line > arguments through our standard conversions, so you could say > --progress=1GHz. At some point I was going to add this myself but never got > around to it. > > Steve > > On Thu, Oct 9, 2008 at 8:53 AM, nathan binkert <[EMAIL PROTECTED]> wrote: >> >> There's m5.event.ProgressEvent. >> >> It's not a command line option, the users's script would have to >> create a progress event. >> >> Nate >> >> On Thu, Oct 9, 2008 at 8:14 AM, Steve Reinhardt <[EMAIL PROTECTED]> wrote: >> > OK... I just tried "--help" and it didn't show up, and then I looked for >> > 'progress' using cscope (which of course only looks at the C++ code) and >> > found only the CPU option. So if it lives exclusively in Python and >> > doesn't >> > have a help string then I could have missed it. >> > >> > Steve >> > >> > On Thu, Oct 9, 2008 at 8:06 AM, nathan binkert <[EMAIL PROTECTED]> wrote: >> >> >> >> I still have it, I'll have to figure out if it's not committed, but it >> >> got moved into python and is a "PythonEvent" subclass now. >> >> >> >> Nate >> >> >> >> On Thu, Oct 9, 2008 at 8:05 AM, Steve Reinhardt <[EMAIL PROTECTED]> >> >> wrote: >> >> > There's a progress_interval parameter on the base CPU object that you >> >> > can >> >> > set which will cause the CPU to print it's progress at the specified >> >> > interval. >> >> > >> >> > I thought there used to be a global progress event that you could get >> >> > to >> >> > print out with a --progress command line argument but I don't see >> >> > that >> >> > anymore... it must have gotten deleted at some point. (Does anyone >> >> > besides >> >> > me remember this? Anyone know what happened to it?) >> >> > >> >> > Steve >> >> > >> >> > On Wed, Oct 8, 2008 at 1:16 PM, Eduardo Olmedo Sanchez >> >> > <[EMAIL PROTECTED]> >> >> > wrote: >> >> >> >> >> >> I;m using the example that comes with the M5 simulator, the one that >> >> >> it's >> >> >> in that configs/example/se.py, If I'm not wrong that one uses the >> >> >> SimpleAtomicCPU, is there any way that the M5 simulator can show me >> >> >> a >> >> >> little >> >> >> of feedback of the simulation, number of cycles or how many of the >> >> >> simulation lefts. Thank you. >> >> >> >> >> >> On Wed, Oct 8, 2008 at 1:08 PM, nathan binkert <[EMAIL PROTECTED]> >> >> >> wrote: >> >> >>> >> >> >>> That's easily possible. Depending on which CPU model you use, you >> >> >>> can >> >> >>> expect something like 1000x slowdown for SimpleAtomicCPU to 50000x >> >> >>> slowdown for O3CPU. >> >> >>> >> >> >>> Nate >> >> >>> >> >> >>> On Wed, Oct 8, 2008 at 12:30 PM, Eduardo Olmedo Sanchez >> >> >>> <[EMAIL PROTECTED]> wrote: >> >> >>> > Hi: >> >> >>> > >> >> >>> > This is the first time that I simulate my own benchmark, and it's >> >> >>> > taken >> >> >>> > a >> >> >>> > long time, and I'd like to ask if it's normal, the execution of >> >> >>> > the >> >> >>> > program >> >> >>> > in my computer takes over 2~5 secons, but the simulation has been >> >> >>> > 1h30m >> >> >>> > and >> >> >>> > it's not finishied. I think that the simulator is correct >> >> >>> > installed, >> >> >>> > because >> >> >>> > I've been able to simulate some simple program such as Hello >> >> >>> > World. >> >> >>> > I'm >> >> >>> > simulating under ALPHA architecture and using SE mode. By the way >> >> >>> > can >> >> >>> > anyone >> >> >>> > tell me how to tell the simulator that prints in the screen some >> >> >>> > info >> >> >>> > about >> >> >>> > the simulation to see if everyithing goes fine. >> >> >>> > >> >> >>> > Thank so much. >> >> >>> > >> >> >>> > _______________________________________________ >> >> >>> > m5-users mailing list >> >> >>> > [email protected] >> >> >>> > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> >> >>> > >> >> >>> _______________________________________________ >> >> >>> m5-users mailing list >> >> >>> [email protected] >> >> >>> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> m5-users mailing list >> >> >> [email protected] >> >> >> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> >> > >> >> > >> >> > _______________________________________________ >> >> > m5-users mailing list >> >> > [email protected] >> >> > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> >> > >> >> _______________________________________________ >> >> m5-users mailing list >> >> [email protected] >> >> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> > >> > >> > _______________________________________________ >> > m5-users mailing list >> > [email protected] >> > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> > >> _______________________________________________ >> m5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
