[gem5-users] Re: Packet VALID_ADDR being cleared when try to resend it !

[Abdlerhman Abotaleb]

After through debugging It appears that the problem happens at the following call: Inside " CoherentXBar::recvTimingReq":             success = memSidePorts[mem_side_port_id]->sendTimingReq(pkt); This "sendTimingReq" appears to cause Pkt modifications. This function actually will end up calling recvTimingReq at the memory controller. I found an intersteing comment few lines before calling this function:      // store the original address as an address mapper could possibly     // modify the address upon a sendTimingRequest     const Addr addr(pkt->getAddr()); I still have no clue what is happening , but this converges the problem search if one can help. Still, if I tried to "print" the packet (i.e. pkt->print()) anywhere on the path (or at least enable CoherentXBar debug flag) , it will cause a segmentation fault! Thank you. regards, Abdelrhman From: Abdlerhman Abotaleb <abota...@mcmaster.ca> Sent: Wednesday, July 13, 2022 11:52 AM To: Balazs Gerofi via gem5-users <gem5-users@gem5.org> Subject: [gem5-users] Packet VALID_ADDR being cleared when try to resend it !   Hi all What does it make a Packet's "VALID_ADDR" flag being cleared , even it was set before? I'm sending some packets from the cache to unblocking memory object that I created  Inside this unblocking memory object, I crated a queue to store packets that fail to be sent After a while , this memory object receives a packet that failed to be sent , so this packet is blocked. Then, I'm inserting the packet to the queue of blocked requests. Inside the recvReqRetry I'm calling  sendTimingReq(pkt). Eventually this packet is sent to CoherentXBar::recvTimingReq it fails there. The following assertion fails: gem5.debug: build/RISCV/mem/packet.hh:832: bool gem5::Packet::isSecure() const: Assertion `flags.isSet(VALID_ADDR)' failed. Even If I tried to enable any packet debugging method (like calling pkt->print()) a segmentation fault arises! I can find only that Packet's flags.clear() happens :       a. happens when constructing a new Packet from request, but even with that the "VALID_ADDR" is being set if it has a PAddr.  (There are two constructors)       b. Another case , is for a third constructor that takes another packet as an argument, but this constructor set the "VALID_ADDR" and "VALID_SIZE" to be the same as the packet being passed.        I can't find anywhere that flags.clear(VALID_ADDR) happens. So, what can be the problem cause? Thank you. regards, Abdelrhman

_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org