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 depending on the vnet, but this function has to be called for the message buffer to be valid].
If all you have changed in the protocol is to broadcast to all L1's and directories, instead only only to L1's, you also need to account for what happens when these directories receive these messages. My guess is that these messages are being inserted into some message buffer that is not part of the protocol specifications and hence this error shows up. - Tushar On Jul 25, 2012, at 5:29 PM, gem5 gem5 wrote: > Hi all, > > I want to modify MOESI_hammer protocol to broadcast all the messages. Since > multicast is supported, I think it's possible to do this. I got some problem > with my first step. When I modify > out_msg.Destination.broadcast(MachineType:L1Cache); to be > out_msg.Destination.broadcast() which I assume means to broadcast to all > nodes, inside of action(fn_forwardRequestIfNecessary, "fn", desc="Forward > requests if necessary"), I got some error like this when run the rubynetwork > tester with Pt2Pt topology: > > panic: Ordering property of has not been set > @ cycle 40 > [enqueue:build/X86_SE/mem/ruby/buffers/MessageBuffer.cc, line 165] > Memory Usage: 241400 KBytes > Program aborted at cycle 40 > Abort > > I tried to set the corresponding virtual network forwardFromDir's > ordered="true", but still I cannot get rid of this error. Any help will be > appreciated. Thanks a lot! > > Jinzhu > > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
