arch/loongarch/include/asm/paravirt.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/asm/paravirt.h

Extension

.h

Size

605 bytes

Lines

36

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/jump_label.h

Detected Declarations

• function pv_ipi_init
• function pv_time_init
• function pv_spinlock_init

Annotated Snippet

#ifndef _ASM_LOONGARCH_PARAVIRT_H
#define _ASM_LOONGARCH_PARAVIRT_H

#ifdef CONFIG_PARAVIRT

#include <linux/jump_label.h>

DECLARE_STATIC_KEY_FALSE(virt_preempt_key);
DECLARE_STATIC_KEY_FALSE(virt_spin_lock_key);
DECLARE_PER_CPU(struct kvm_steal_time, steal_time);

int __init pv_ipi_init(void);
int __init pv_time_init(void);
int __init pv_spinlock_init(void);

#else

static inline int pv_ipi_init(void)
{
	return 0;
}

static inline int pv_time_init(void)
{
	return 0;
}

static inline int pv_spinlock_init(void)
{
	return 0;
}

#endif // CONFIG_PARAVIRT
#endif

Annotation

• Immediate include surface: `linux/jump_label.h`.
• Detected declarations: `function pv_ipi_init`, `function pv_time_init`, `function pv_spinlock_init`.
• Atlas domain: Architecture Layer / arch/loongarch.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.