|
gem5
v22.1.0.0
|
Classes | |
| struct | PacketInfo |
| A struct to hold on to the essential fields from a packet, so that the packet and underlying request can be safely passed on, and consequently modified or even deleted. More... | |
Typedefs | |
| typedef ProbePointArg< PacketInfo > | Packet |
| Packet probe point. More... | |
| typedef std::unique_ptr< Packet > | PacketUPtr |
| typedef ProbePointArg< uint64_t > | PMU |
| PMU probe point. More... | |
| typedef std::unique_ptr< PMU > | PMUUPtr |
| typedef ProbePointArg<PacketInfo> gem5::probing::Packet |
Packet probe point.
This probe point provides a unified interface for components that want to instrument Packets in the memory system. Components should when possible adhere to the following naming scheme:
PktRequest: Requests sent out on the memory side of a normal components and incoming requests for memories. Packets should not be duplicated (i.e., a packet should only appear once irrespective of the receiving end requesting a retry).
PktResponse: Response received from the memory side of a normal component or a response being sent out from a memory.
PktRequestCPU: Incoming, accepted, memory request on the CPU side of a two-sided component. This probe point is primarily intended for components that cache or forward requests (e.g., caches and XBars), single-sided components should use PktRequest instead. The probe point should only be called when a packet is accepted.
PktResponseCPU: Outgoing response memory request on the CPU side of a two-sided component. This probe point is primarily intended for components that cache or forward requests (e.g., caches and XBars), single-sided components should use PktRequest instead.
| typedef std::unique_ptr<Packet> gem5::probing::PacketUPtr |
| typedef ProbePointArg<uint64_t> gem5::probing::PMU |
| typedef std::unique_ptr<PMU> gem5::probing::PMUUPtr |