[m5-dev] setting M5_PATH for the regressions

Independent of how the specifics end up hashed out, I think it's safe to say it would be a good idea to set M5_PATH explicitly for the regressions instead of relying on the default built into M5 being tuned for that environment. I'd like to attempt to do that now. Does anyone object? Could

[m5-dev] changeset in m5: configs: set default cache params

changeset 8fe2d7ff in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=8fe2d7ff description: configs: set default cache params It's confusing (especially to new users), when you are setting some standard parameters (as defined in Options.py) and they

[m5-dev] changeset in m5: ruby: extend dprintfs for RubyGenerated TraceFlag

changeset e1fd27c723a2 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=e1fd27c723a2 description: ruby: extend dprintfs for RubyGenerated TraceFlag "executing" isnt a very descriptive debug message and in going through the output you get multiple messages

[m5-dev] changeset in m5: ruby: cleaning up RubyQueue and RubyNetwork dpr...

changeset 9138d38eccd7 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=9138d38eccd7 description: ruby: cleaning up RubyQueue and RubyNetwork dprintfs Overall, continue to progress Ruby debug messages to more of the normal M5 debug message style -

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

Quoting Ali Saidi : On Feb 22, 2011, at 5:25 PM, Gabe Black wrote: Like I said, why can't you just do that with a simple bash alias that appends the options to the binary? Or a wrapper script? Why make a new tool when an existing one works just as well? I don't think any of those mechanisms

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

Quoting Ali Saidi : Regarding /dist: I think the directories of interest were binaries, disks, cpu2000. What more of a rundown do you want? That's not what I meant. I meant why is /dist in /dist at all? Where did /dist come from? I've never seen it anywhere else. Everything else puts

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

On Feb 22, 2011, at 5:25 PM, Gabe Black wrote: > Like I said, why can't you just do that with a simple bash alias that > appends the options to the binary? Or a wrapper script? Why make a new > tool when an existing one works just as well? I don't think any of those mechanisms are that great. Wra

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

On 02/22/11 15:23, Ali Saidi wrote: > > On 2/23/11 3:49 AM, "Gabe Black" wrote: > >> On 02/22/11 09:33, nathan binkert wrote: 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

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

On 2/23/11 3:49 AM, "Gabe Black" wrote: >On 02/22/11 09:33, nathan binkert wrote: >>> 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 generating scr

[m5-dev] MOESI_CMP_directory-perfectDir.sm

Hi All, I just posted a patch that removes all of the protocol files that are not supported in gem5. However, I'm not sure if anyone has used/is using the file MOESI_CMP_directory-perfectDir.sm. I've never used it before and I have no idea if it even works or what exactly it is supposed to do

[m5-dev] Review Request: ruby: removed unsupported protocol files

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/493/ --- Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binke

[m5-dev] Review Request: ruby: cleaned up access permission enum

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/494/ --- Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binke

[m5-dev] Review Request: MOESI_hammer: cache probe address clean up

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/495/ --- Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binke

[m5-dev] Review Request: ruby: automate permission setting

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/496/ --- Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binke

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

On 02/22/11 09:33, nathan binkert wrote: >> 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 generating script would have to >> be fairly smart too so you cou

Re: [m5-dev] Review Request: ruby: cleaning up RubyQueue and RubyNetwork dprintfs

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/489/#review881 --- Ship it! - Brad On 2011-02-22 13:11:15, Korey Sewell wrote: > > --

Re: [m5-dev] Review Request: ruby: cleaning up RubyQueue and RubyNetwork dprintfs

OK, sorry for the double-update here... But I think this patch is ready to go. If/when it gets approved, I'll push the other ruby dprintf update patch ... On Tue, Feb 22, 2011 at 4:11 PM, Korey Sewell wrote: >This is an automatically generated e-mail. To reply, visit: > http://reviews.m5si

Re: [m5-dev] Review Request: ruby: cleaning up RubyQueue and RubyNetwork dprintfs

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/489/ --- (Updated 2011-02-22 13:11:15.700425) Review request for Default, Ali Saidi, Gabe Bl

Re: [m5-dev] Review Request: ruby: cleaning up RubyQueue and RubyNetwork dprintfs

--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/489/ --- (Updated 2011-02-22 13:06:28.829795) Review request for Default, Ali Saidi, Gabe Bl

Re: [m5-dev] Review Request: ruby: cleaning up RubyQueue and RubyNetwork dprintfs

> On 2011-02-18 13:33:14, Nathan Binkert wrote: > > src/mem/ruby/network/simple/Throttle.cc, line 253 > > > > > > ccprintf() > > Korey Sewell wrote: > In general, is it just a matter of preference or M5 style to do > {

Re: [m5-dev] Review Request: ruby: cleaning up RubyQueue and RubyNetwork dprintfs

> On 2011-02-18 13:33:14, Nathan Binkert wrote: > > src/mem/ruby/buffers/MessageBuffer.cc, line 58 > > > > > > How does the name get set now? This was an error, I shouldnt have taken this out. > On 2011-02-18 13:33:14, Nat

Re: [m5-dev] changeset in m5: m5: merged in hammer fix

I apologize for the multiple merges, but I assure you it was not because I was negligent. Instead, it was cause by some technical issues beyond my control. The merges don't conflict with the same files, so I think the impact should be minimal. Brad > -Original Message- > From: m5-dev

[m5-dev] changeset in m5: m5: merged in hammer fix

changeset e6ce478c05d3 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=e6ce478c05d3 description: m5: merged in hammer fix diffstat: LICENSE | 2 +- README

[m5-dev] changeset in m5: merged with Ali X11 patch

changeset 43a279c3cde2 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=43a279c3cde2 description: merged with Ali X11 patch diffstat: src/mem/protocol/MOESI_hammer-cache.sm | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diffs (19 lines): diff -r 9aab11bcd84

[m5-dev] changeset in m5: MOESI_hammer: fixed wakeup for SS->S transistion

changeset c7f591ccf3a1 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=c7f591ccf3a1 description: MOESI_hammer: fixed wakeup for SS->S transistion diffstat: src/mem/protocol/MOESI_hammer-cache.sm | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diffs (19 lines

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

> 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 generating script would have to > be fairly smart too so you could quickly update particular fields, remove >

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

> Oh, actually, this made me think of something I wanted to bring up. What > we're talking about now is basically a config file, but we already have > something called that. I was describing M5 to some folks at work a little > while ago, and there seemed to be some confusion about how configuration

[m5-dev] Cron /z/m5/regression/do-regression quick

* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux

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

Oh, actually, this made me think of something I wanted to bring up. What we're talking about now is basically a config file, but we already have something called that. I was describing M5 to some folks at work a little while ago, and there seemed to be some confusion about how configuration