Hi Andreas, What you say is true for an interconnect-like module that uses a "normal" request to create a "snoop" request.
But, in my case, I have to create a snoop request from scratch because this snoop request originally is from an interconnect-like module in a different bus protocol domain. Can this scenario be supported? Thanks, Uday From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Hansson Sent: Monday, June 24, 2013 2:41 PM To: gem5 users mailing list Subject: Re: [gem5-users] masterID for snooping Hi Uday, If you need to send requests I would imagine you want a master port. A snoop request would typically be created from a "normal" request and thus copy its master id. Andreas From: <Ranga>, L Udaya <[email protected]<mailto:[email protected]>> Reply-To: gem5 users mailing list <[email protected]<mailto:[email protected]>> Date: Monday, 24 June 2013 09:45 To: gem5 users mailing list <[email protected]<mailto:[email protected]>> Subject: [gem5-users] masterID for snooping Hi, I have a module (derived from SimpleMemory) which has an instance of type 'SlavePort'. I need to call sendTimingSnoopReq( PacketPtr ) on this port. For this I have to first create a Request and then Packet. Request() constructor needs a mastered. I understand that typically this is obtained at init time by calling getMasterID from System. But, I have SimpleMemoryParams which doesn't have handle to System. How do I obtain masterID for sending a snoop Request? Thanks, Uday -- 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.
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
