arch/loongarch/include/asm/kvm_ipi.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/asm/kvm_ipi.h

Extension

.h

Size

876 bytes

Lines

46

Domain

Architecture Layer

Bucket

arch/loongarch

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• kvm/iodev.h

Detected Declarations

• struct loongarch_ipi
• struct ipi_state

Annotated Snippet

struct loongarch_ipi {
	spinlock_t lock;
	struct kvm *kvm;
	struct kvm_io_device device;
};

struct ipi_state {
	spinlock_t lock;
	uint32_t status;
	uint32_t en;
	uint32_t set;
	uint32_t clear;
	uint64_t buf[4];
};

#define IOCSR_IPI_BASE		0x1000
#define IOCSR_IPI_SIZE		0x160

#define IOCSR_IPI_STATUS	0x000
#define IOCSR_IPI_EN		0x004
#define IOCSR_IPI_SET		0x008
#define IOCSR_IPI_CLEAR		0x00c
#define IOCSR_IPI_BUF_20	0x020
#define IOCSR_IPI_BUF_28	0x028
#define IOCSR_IPI_BUF_30	0x030
#define IOCSR_IPI_BUF_38	0x038
#define IOCSR_IPI_SEND		0x040
#define IOCSR_MAIL_SEND		0x048
#define IOCSR_ANY_SEND		0x158

int kvm_loongarch_register_ipi_device(void);

#endif

Annotation

• Immediate include surface: `kvm/iodev.h`.
• Detected declarations: `struct loongarch_ipi`, `struct ipi_state`.
• Atlas domain: Architecture Layer / arch/loongarch.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.