Hi Urmish, The panic is simply a sanity check I put in place in the port to ensure that we do not unintentionally introduce buffers where there should not be any.
In this case it seems there are a lot of packets building up in the cache, waiting to be sent to the LSQ (either responses, or snoop requests). I am not quite sure what is regulating the rate of these packets being sent to the core (I would think one per cycle), so it would be good if you could run with a few debug flags to iron out what is happening. PacketQueue, Cache, LSQ, LSQUnit is probably a good start. Thanks, Andreas On 02/01/2015 22:05, "Urmish Ajit Thakker via gem5-dev" <[email protected]> wrote: >Hi, > >I was experimenting with the impact of Lq/SQ size on performance. When I >changed the LQ/SQ Size to 128 I get the following error - > >panic: Packet queue system.cpu.dcache.cpu_side-CpuSidePort has grown >beyond 100 packets > @ tick 2920099746500 >[schedSendTiming:build/ARM/mem/packet_queue.cc, line 121] > >Could someone help we understand this error? > >Regards, >Urmish >_______________________________________________ >gem5-dev mailing list >[email protected] >http://m5sim.org/mailman/listinfo/gem5-dev > -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782 _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
