*
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory
passed.
*
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory
passed.
*
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#337 - Checkpoint Tester Identifies Mismatches (Bugs) for X86_FS
User who did this: - Gabe Black (gblack)
--
I looked at this, and there are still some problems with your command
line.
1.
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/396/#review796
---
src/arch/x86/pagetable_walker.cc
You're headed in the right direction but aren't quite there yet. If you
split out the functional part of startWalk into its own function, you
can change the signature and pass the address and size by reference.
Then you don't need a request or translation object at all. You could
even put that
You should be able to move that around any other patches ahead of it,
right? It's so simple I wouldn't expect it to really depend on the
intervening patches.
Gabe
Beckmann, Brad wrote:
Hi Nilay,
Yes, I am aware of this problem and one of the patches
(http://reviews.m5sim.org/r/381/) I'm
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/392/#review798
---
What's the difference between RMW and its locked version? I know that
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/392/#review799
---
What's the difference between RMW and its locked version? I know that
Hi Nilay,
You are mostly correct. I believe this patch contains two things
1. Support in SLICC to allow waiting and stalling on messages in message
buffer when the directory is in blocking state for that address (i.e.
can not process the message at this point), until some event
