[m5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick

2011-02-21 Thread Cron Daemon
scons: *** Source `tests/quick/00.hello/ref/alpha/linux/simple-timing-ruby-MOESI_hammer/stats.txt' not found, needed by target `build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer/status'. *

[m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabe Black
Hi folks. I said a while ago I intended to change how various files needed by M5 were located, and this weekend I started looking into actually doing that. The first thing I think I'm going to do is keep the end behavior basically the same but adjust how SysPaths.py works to make it more amenable

Re: [m5-dev] Review Request: ruby: extend dprintfs for RubyGenerated TraceFlag

2011-02-21 Thread Nilay Vaish
--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/492/#review877 --- Ship it! - Nilay On 2011-02-18 14:55:40, Korey Sewell wrote:

Re: [m5-dev] Review Request: ruby: extend dprintfs for RubyGenerated TraceFlag

2011-02-21 Thread Brad Beckmann
--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/492/#review878 --- Ship it! - Brad On 2011-02-18 14:55:40, Korey Sewell wrote:

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Ali Saidi
Nate, Didn't you create a .m5 config file to do some of this at one point? Ali On Feb 21, 2011, at 4:40 PM, Gabe Black wrote: As far as actual changes to the way paths are resolved, I was thinking the following. Right now, the directories in M5_PATH (or the defaults) are walked through

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabe Black
As far as actual changes to the way paths are resolved, I was thinking the following. Right now, the directories in M5_PATH (or the defaults) are walked through one at a time, and if one exists it becomes system.dir. When the path for a disk image, etc., is needed, it's formed by taking that

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabe Black
Since I think Nate is occupied right now, I grepped for .m5 and found what I think you're talking about in src/python/m5/coinfig.py. It looks like it's basically a folder you can put in your home directory where M5 will automatically look for config files. We could roll that into this too,

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabe Black
Actually digging a bit deeper, it looks like .m5 is where you put an options.py script which you can use to add new command line options to M5. That's set up in main.py, and a comment there says its for letting people set default options, I suppose so you don't have to pass them on the command

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Ali Saidi
I seem to remember being able to change things like SysPaths in it, or at least how Nate intended it to work. Of course, there's no documentation about it and the code is confusing, so i dunno... Let me ponder the other stuff in this for a day or two... Ali On Feb 21, 2011, at 7:56 PM, Gabe

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread nathan binkert
I seem to remember being able to change things like SysPaths in it, or at least how Nate intended it to work. Of course, there's no documentation about it and the code is confusing, so i dunno... Let me ponder the other stuff in this for a day or two... What's confusing? I added it mostly

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabe Black
On 02/21/11 18:37, nathan binkert wrote: I seem to remember being able to change things like SysPaths in it, or at least how Nate intended it to work. Of course, there's no documentation about it and the code is confusing, so i dunno... Let me ponder the other stuff in this for a day or

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread nathan binkert
I don't know if we should expect people to reach into main.py like that in a per user way. It does the job setting default values, but does anybody use that even? Nobody seems to have known it existed. I think setting an environment variable is a lot more straightforward than writing a python

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabe Black
On 02/21/11 20:14, nathan binkert wrote: I don't know if we should expect people to reach into main.py like that in a per user way. It does the job setting default values, but does anybody use that even? Nobody seems to have known it existed. I think setting an environment variable is a lot

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Ali Saidi
On Feb 21, 2011, at 10:15 PM, Gabe Black wrote: On 02/21/11 20:14, nathan binkert wrote: I don't know if we should expect people to reach into main.py like that in a per user way. It does the job setting default values, but does anybody use that even? Nobody seems to have known it existed. I

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabriel Michael Black
Three places does seem like a lot. What are they specifically? Hopefully we can get rid of one or two. That said, using python to generate python to put in a hidden directory to read with python embedded in a binary is, in my opinion, WAY more complicated than the problem warrants. The

Re: [m5-dev] paths for disk images, kernels, etc.

2011-02-21 Thread Gabriel Michael Black
Quoting Ali Saidi sa...@umich.edu: Let me ponder the other stuff in this for a day or two... Ali Speaking of the other stuff, could anyone give a quick rundown of /dist? Gabe ___ m5-dev mailing list m5-dev@m5sim.org