Module reply 

IPC call/reply support : both synchronous (blocking) and async (ring-based).

Design concept

• ReplyTarget::Sync is analogous to an seL4 endpoint call+reply
• ReplyTarget::AsyncRing combines both: the ring is the completion port
• Send/Receive/Reply : exactly our sync wait_for_reply/deliver_reply
• The CQE user_data correlates the reply to the original submission

Structs

ReplyRegistry 🔒

ReplySlot 🔒

Enums

ReplyTarget 🔒

Describes how to deliver a reply once the server responds.

Statics

REPLIES 🔒

Functions

cancel_replies_waiting_on

deliver_reply

Deliver a reply message to the given task.

epipe_reply 🔒

push_completion_for_ring_by_id 🔒

Thin wrapper : resolve ring_id to &Ring and then push CQE.

register_ring_call

Register a pending ring-based IpcCall for caller.

wait_for_reply

Block the current task waiting for a reply message (synchronous call path).