arch/loongarch/include/asm/kvm_dmsintc.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/asm/kvm_dmsintc.h

Extension

.h

Size

639 bytes

Lines

28

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kvm_types.h

Detected Declarations

• struct loongarch_dmsintc
• struct dmsintc_state

Annotated Snippet

struct loongarch_dmsintc {
	struct kvm *kvm;
	uint64_t msg_addr_base;
	uint64_t msg_addr_size;
	uint32_t cpu_mask;
};

struct dmsintc_state {
	atomic64_t vector_map[4];
};

int kvm_loongarch_register_dmsintc_device(void);
void dmsintc_inject_irq(struct kvm_vcpu *vcpu);
int dmsintc_set_irq(struct kvm *kvm, u64 addr, int data, int level);
int dmsintc_deliver_msi_to_vcpu(struct kvm *kvm, struct kvm_vcpu *vcpu, u32 vector, int level);

#endif

Annotation

• Immediate include surface: `linux/kvm_types.h`.
• Detected declarations: `struct loongarch_dmsintc`, `struct dmsintc_state`.
• Atlas domain: Architecture Layer / arch/loongarch.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.