It is node 3, vnet 1, but vnet=1 corresponds to the
MessageBuffer goo, network="From", virtual_network="1", ordered="false";
And "goo" corresponds to the "goo_in". port
in_port(goo_in, RequestMsg, goo) {
if (goo_in.isReady()) {
peek(goo_in, RequestMsg) {
assert(false);
}
}
}
As for the node 3, it just comes up on that because of how the thread gets
scheduled onto that node.
Malek
On Tue, May 17, 2011 at 3:39 PM, Korey Sewell <ksew...@umich.edu> wrote:
> >
> > panic: Ordering property of fromNet node 3 j 1 has not been set
> > @ cycle 2453317927500
> >
> >
> [enqueue:build/ALPHA_FS_MOESI_CMP_directory/mem/ruby/buffers/MessageBuffer.cc,
> > line 170]
> >
> Are you sure that's not node 3, vnet 1???
>
> --
> - Korey
> _______________________________________________
> gem5-dev mailing list
> gem5-dev@m5sim.org
> http://m5sim.org/mailman/listinfo/gem5-dev
>
_______________________________________________
gem5-dev mailing list
gem5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/gem5-dev
