On Fri, 26 Oct 2012, tejasi pimpalkhute wrote:
Hi Nilay,
I have gone through the whole documentation of gem5 but I am still unable
to figure out why the flit_d lacks information about its destination's
physical address and data request type(i.e. if the request is read/write)
and if that is corr
Hi Nilay,
I have gone through the whole documentation of gem5 but I am still unable
to figure out why the flit_d lacks information about its destination's
physical address and data request type(i.e. if the request is read/write)
and if that is correct, from where can I retrieve this information? C
On Tue, October 9, 2012 6:16 pm, tejasi pimpalkhute wrote:
> Thanks, Nilay. I can know the ranks and banks from the physical address
> (datatype physical_address_t) which I get from MemoryMsg or RubyRequest
> but
> my main issue is how to extract that information from a single flit. As
> per
> the
Thanks, Nilay. I can know the ranks and banks from the physical address
(datatype physical_address_t) which I get from MemoryMsg or RubyRequest but
my main issue is how to extract that information from a single flit. As per
the current code, I can only get a msg_ptr from it of type Message*. I am
a
On Thu, 4 Oct 2012, tejasi pimpalkhute wrote:
Thanks a ton for explaining this, I think I was mistaken earlier. In that
case, can I know beforehand the physical address of the request flits which
will be going to the directory controller? Can I calculate the rank and
When router forwards a fli
Thanks a ton for explaining this, I think I was mistaken earlier. In that
case, can I know beforehand the physical address of the request flits which
will be going to the directory controller? Can I calculate the rank and
bank address of that flit as done in the memory controller (if the router
has
On Thu, 4 Oct 2012, tejasi pimpalkhute wrote:
Hi Nilay,
Thanks for throwing light on this. I want to arbitrate request packets
originated the core (requiring off-chip memory access) at the router. Do
you think this is possible in Gem5?
My understanding was that both the memory request flits as
Hi Nilay,
Thanks for throwing light on this. I want to arbitrate request packets
originated the core (requiring off-chip memory access) at the router. Do
you think this is possible in Gem5?
My understanding was that both the memory request flits as well as network
flits are routed via interconnec
On Tue, 2 Oct 2012, tejasi pimpalkhute wrote:
Hi Tushar,
Thanks for looking into the code, I tried running the Network_test protocol
and got this error:
Global frequency set at 10 ticks per second
info: Entering event queue @ 0. Starting simulation...
gem5.debug:
build/ALPHA_SE_Networ
Hi Tushar,
Thanks for looking into the code, I tried running the Network_test protocol
and got this error:
Global frequency set at 10 ticks per second
info: Entering event queue @ 0. Starting simulation...
gem5.debug:
build/ALPHA_SE_Network_test/mem/ruby/network/garnet/fixed-pipeline/Inp
Hi Tejasi,
Try testing your code with the NetworkTest protocol and inject a fixed number
of packets and see if they get delivered. If not, see why some flits might be
stuck at some routers.
While I didn't go through your entire code in detail, I see you have some wait
cycles etc for each input p
Hi Nilay and Tushar,
I got rid of that error by writing a check for memory message and network
message in the SWallocator_d.cc. However, I am getting a deadlock error now
when I run the same test. I get this error:
panic: Deadlock detected: current_time: 50001 last_progress_time: 0
difference: 5
On Wed, 26 Sep 2012, tejasi pimpalkhute wrote:
Hi Nilay and Tushar,
Thanks for your response. I thought so earlier but I tried running pure
memory test (e.g. ruby_mem_test.py) as well as ruby_random_test. Shouldn't
the memory test inject only memory request packets in the network? In that
case
Hi Nilay and Tushar,
Thanks for your response. I thought so earlier but I tried running pure
memory test (e.g. ruby_mem_test.py) as well as ruby_random_test. Shouldn't
the memory test inject only memory request packets in the network? In that
case why should the type cast fail? Please correct me
If the Message* is not a MemoryMsg*, then safe cast will fail.
--
Nilay
On Wed, 26 Sep 2012, Tushar Krishna wrote:
Hi Tejasi,
I tried it too and yeah it fails, not sure why...
The same code works in src/mem/ruby/system/RubyMemoryControl.cc
A cast into NetworkMessage has been done in places li
Hi Tejasi,
I tried it too and yeah it fails, not sure why...
The same code works in src/mem/ruby/system/RubyMemoryControl.cc
A cast into NetworkMessage has been done in places like RoutingUnit_d but that
won't give you the message type.
You'll have to dig in and see why the cast fails…
- Tushar
Hi Tushar,
I had resumed working on this again, so was going through your
emails(please see email below). I am still getting this error:
gem5.debug: build/ALPHA_SE_MOESI_hammer/base/cast.hh:49: T safe_cast(U)
[with T = const MemoryMsg*, U = Message*]: Assertion `ret' failed.
Program aborted at cy
17 matches
Mail list logo
