Hi Jinzhu,
Ok so I see two components in your design:
(1) broadcast-based coherence protocol
(2) shared-bus based crossbar
For (1) you want every message to be a broadcast. I am not sure if MOESI_hammer
is the correct protocol to use as your starting point. The reason is that
MOESI_hammer is es
Thanks for the hint Ali.
Going over the trace from instruction queue, I am almost positive it is a
FloatAdd.
system.cpu0.fetch: [tid:0]: Instruction PC 0x8986 (0) created [sn:8792].
system.cpu0.fetch: [tid:0]: Instruction is: ldrneon8_uop.w
system.cpu0.iq: Instruction is ready to issue, putting
On 26.07.2012 19:44, Amin Farmahini wrote:
> Hi,
>
> I'd like to
change the latency of a couple of Neon instructions. I started with VLD1
instruction which is called ldrNeon in Gem5. This instruction is
classified as a "FloatAdd" opClass. So I can modify the latency (opLat)
of "FloatAdd" clas
Hi,
I'd like to change the latency of a couple of Neon instructions. I started
with VLD1 instruction which is called ldrNeon in Gem5. This instruction is
classified as a "FloatAdd" opClass. So I can modify the latency (opLat) of
"FloatAdd" class in O3_ARM_v7a.py file. However, this obviously chang
Tushar,
The reason I am modifying the protocol is that I want to implement a
shared-bus based crossbar where each node has its own dedicated write
channel and other nodes listen to it. However, I see that ruby does not
support hardware broadcast, so modifying the protocol seems to me the only
way
Hi Jinzhu,
Why do you want to broadcast to L1s and the directories? Just to add more
messages in the network? MOESI_hammer inherently broadcasts to all L1s which
gives you a broadcast to all nodes. I don't think you should mess with the
protocol, unless you have a strong justification for why th
Hi Tushar,
Thanks for your reply! I think you are right. I need to deal with those
extra messages. Any suggestions how to do that? Should I define some new
transitions and get rid of those messages?
I have read your 1 to many paper before. If I want to implement some
crossbar topology which supp
The error has nothing to do with the virtual network being ordered or not.
If you look at MessageBuffer.hh, line 131, a setOrdering function needs to be
called for each MessageBuffer.
This is called from the coherence protocol's generated files. [The ordering
itself might be true or false dependi
I agree with Mahmood, try to run the statically compiled binaries first and
apply the patches if you experience issues.
-Andrea
On Thu, Jul 26, 2012 at 4:41 AM, Mahmood Naderan wrote:
> You can run binaries with gem5 SE. If you don't see such "unimplemented
> syscall" error, then everything is
You can run binaries with gem5 SE. If you don't see such "unimplemented
syscall" error, then everything is fine.
// Naderan *Mahmood;
On Thu, Jul 26, 2012 at 5:35 AM, wael Amr wrote:
> Hi Eng. Andrea,
>
> Thanks for your your reply.
> I found the link for downloading the SPEC2000 benchmarks
10 matches
Mail list logo
