Hi,
I have a few traces that I recorded at the input port of the directory (CHI protocol). I would like to replay these by injecting them directly into the Ruby network/directory. Requests in these traces contain information about the type of coherent request/snoop response they send and I want to inject traffic that includes this. Looking around, I found that the Garnet standalone protocol does something similar since all it does is inject traffic into the network. Is combining the Garnet standalone protocol with the CHI model the only way to send messages to the directory? Or are there other approaches that directly inject coherent traffic into the directory (without the need for a sequencer or dummy cache)?
Thanks,
Vishnu
Hi Vishnu,
I do not believe there is any way to direct traffic to a particular message
buffer (e.g, requestToDir
). Ruby is in some sense a "black box" that only
has port inputs (which are directed to a sequencer) and port output (via
requestToMemory
).
That said, this is a cool idea! I would encourage you to develop this
support if it's something that you would find useful for your work. In
fact, I think this support could be very useful upstream for testing!
Cheers,
Jason
On Wed, Jul 26, 2023 at 5:52 AM VISHNU RAMADAS via gem5-users <
gem5-users@gem5.org> wrote:
Hi,
I have a few traces that I recorded at the input port of the directory
(CHI protocol). I would like to replay these by injecting them directly
into the Ruby network/directory. Requests in these traces contain
information about the type of coherent request/snoop response they send and
I want to inject traffic that includes this. Looking around, I found that
the Garnet standalone protocol does something similar since all it does is
inject traffic into the network. Is combining the Garnet standalone
protocol with the CHI model the only way to send messages to the
directory? Or are there other approaches that directly inject coherent
traffic into the directory (without the need for a sequencer or dummy
cache)?
Thanks,
Vishnu
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.org