scons: *** [build/ALPHA_SE/python/swig/trace_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/debug_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/core_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/event_wrap.fo] Error 1
scons: ***
changeset 5437a0eeb822 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=5437a0eeb822
description:
Object print bug fix
diffstat:
1 file changed, 1 insertion(+)
src/mem/ruby/common/DataBlock.hh |1 +
diffs (11 lines):
diff -r 17e885fd7246 -r 5437a0eeb822
changeset 9082a3fe5608 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=9082a3fe5608
description:
Somayeh's MESI protocol with Polina's bug fixes
diffstat:
4 files changed, 467 insertions(+), 161 deletions(-)
src/mem/protocol/MESI_CMP_directory-L1cache.sm | 108
changeset 737662612eb7 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=737662612eb7
description:
Config adjustments for MESI
diffstat:
3 files changed, 88 insertions(+), 30 deletions(-)
src/mem/ruby/config/TwoLevel_SplitL1UnifiedL2.rb | 36 +-
I'm guessing that this changes the regression results. Did you re-run them?
Nate
On Fri, Sep 11, 2009 at 8:58 AM, pdud...@gmail.com wrote:
changeset deb20a55147c in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=deb20a55147c
description:
MI data corruption bug fix
Those are still broken on zizzer, by the way. We should really fix those
soon so we don't discover a big mess when we finally do.
Gabe
nathan binkert wrote:
I'm guessing that this changes the regression results. Did you re-run them?
Nate
On Fri, Sep 11, 2009 at 8:58 AM,
Those are still broken on zizzer, by the way. We should really fix those
soon so we don't discover a big mess when we finally do.
Anyone got some free time to work on this?
Nate
___
m5-dev mailing list
m5-dev@m5sim.org
Sorry, but I absolutely do not... Have to mail my thesis to Rackham on
Wed! It's very exciting.
Lisa
On Fri, Sep 11, 2009 at 11:24 AM, nathan binkert n...@binkert.org wrote:
Those are still broken on zizzer, by the way. We should really fix those
soon so we don't discover a big mess
changeset 3b2d7fdff6b1 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=3b2d7fdff6b1
description:
Added new MESI files
diffstat:
2 files changed, 214 insertions(+)
src/mem/protocol/MESI_CMP_directory-dma.sm | 139
Hi All,
Attached is a patch I would like to check in that allows Ruby to support
a very large memory address space and high core count. Currently ruby
uses a flat array to store the memory state of the system. This works
well when the simulated system is roughly 4 GB or less, but is not
I finally read this diff. My comments are inline. In the future,
please use hg email which is found in the patchbomb extension. It
makes it far easier to comment on diffs since I can just then reply to
the e-mail without having to jump through hoops to get it into my
mailer.
Nate
diff -r
Attached is a patch I would like to check in that allows Ruby to support a
very large memory address space and high core count. Currently ruby uses a
flat array to store the memory state of the system. This works well when
the simulated system is roughly 4 GB or less, but is not practical
That reminds me. Why do we have a convention of read/set? Why not
read/write or set/get? It seems a little asymmetric, but admittedly
probably not important enough to change in any case.
I have no idea, but if you want to change it, I'd suggest read/write.
Maybe at some point write meant
On Wed, Sep 9, 2009 at 10:47 AM, Gabriel Michael Black
gbl...@eecs.umich.edu wrote:
As far as how often those functions are called, the read one will be called
fairly often for address translation, and potentially in the predecoder
depending on the ISA. The writing one is likely called
14 matches
Mail list logo
