[ESI] Snoop op

[teqdruid]

The 'snoop' operation allows something to spy on a channel. It simply exposes the internal signals combinationally.

[teqdruid]

I'm sure I missed a few places where channel users are checked, but I can't make anything fail.

[mortbopet]

Why have specialized snoop operations for each signaling standard (snoop.vr)?. As opposed to having a snoop op which returns an esi.channel that you unwrap. Then it's all in the lowerings to properly source/sink that esi.channel that is returned by the snoop op, s.t. it doesn't interact with the transactional signals of the snooped link - and, in lower ESI to HW, wrt. the snoop <-> channel interaction, you'd have only a single case to check.

[teqdruid]

The unwrap operations take backpressure as an input signal (argument), rather than the output (result) we want.

…

On Sun, Jan 19, 2025, 3:13 PM Morten Borup Petersen < ***@***.***> wrote: Why have specialized snoop operations for each signaling standard ( snoop.vr)?. As opposed to having a snoop op which returns an esi.channel that you unwrap. Then it's all in the lowerings to properly source/sink that esi.channel that is returned by the snoop op, s.t. it doesn't interact with the transactional signals of the snooped link - and, in lower ESI to HW, wrt. the snoop <-> channel interaction, you'd have only a single case to check. — Reply to this email directly, view it on GitHub <#8096 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALNXYF3CNFLOC4UOLFWF2T2LP2PJAVCNFSM6AAAAABVND7SJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHE4DMMJXGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>