STRUCT VIRTPROC_INFO(9)

okay bestie, pull up a seat — this is struct virtproc_info(9) from the Kernel API Manual 💖✨

🎀 NAME 🎀

struct virtproc_info — virtual remote processor state, no cap 💅

✨ SYNOPSIS ✨

Here’s the struct in all its glory, bestie — every field exactly as it appears:

struct virtproc_info {
    struct virtio_device *vdev;
    struct virtqueue *rvq, *svq;
    void *rbufs, *sbufs;
    unsigned int num_bufs;
    unsigned int buf_size;
    int last_sbuf;
    dma_addr_t bufs_dma;
    struct mutex tx_lock;
    struct idr endpoints;
    struct mutex endpoints_lock;
    wait_queue_head_t sendq;
};

🫶 Members 🫶

• vdev — the virtio device, literally the main character here 💅
• rvq — rx virtqueue
• svq — tx virtqueue
• rbufs — kernel address of rx buffers
• sbufs — kernel address of tx buffers
• num_bufs — total number of buffers for rx and tx
• buf_size — size of one rx or tx buffer
• last_sbuf — index of last tx buffer used
• bufs_dma — dma base addr of the buffers
• tx_lock — protects svq and sbufs, to allow concurrent senders. Sending a message might require waking up a dozing remote processor, which involves sleeping, hence the mutex. So yeah — it’s a mutex because sleep is involved 😭
• endpoints — idr of local endpoints, allows fast retrieval
• endpoints_lock — lock of the endpoints set
• sendq — wait queue of sending contexts waiting for a tx buffers

🌸 Description 🌸

This structure stores the rpmsg state of a given virtio remote processor device — and heads up, there might be several virtio proc devices for each physical remote processor. It’s giving “state keeper for the rpmsg vibes” ✨🦋

🔥 SEE ALSO 🔥

Kernel file ./drivers/rpmsg/virtio_rpmsg_bus.c — go read it, bestie — plus these cuties:

• struct rpmsg_hdr(9)
• struct virtio_rpmsg_channel(9)
• rpmsg_sg_init(9)
• __ept_release(9)
• __rpmsg_destroy_ept(9)
• rpmsg_send_offchannel_raw(9)

mwah 💋 this page was served fresh from ./drivers/rpmsg in October 2026 — struct virtproc_info(9), Kernel API Manual, periodt. 🫶✨