arch/powerpc/include/asm/kvm_para.h
Source file repositories/reference/linux-study-clean/arch/powerpc/include/asm/kvm_para.h
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/include/asm/kvm_para.h- Extension
.h- Size
- 752 bytes
- Lines
- 44
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- 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.
Dependency Surface
asm/kvm_guest.huapi/asm/kvm_para.h
Detected Declarations
function kvm_para_availablefunction kvm_arch_para_featuresfunction kvm_arch_para_hintsfunction kvm_check_and_clear_guest_paused
Annotated Snippet
#ifndef __POWERPC_KVM_PARA_H__
#define __POWERPC_KVM_PARA_H__
#include <asm/kvm_guest.h>
#include <uapi/asm/kvm_para.h>
static inline int kvm_para_available(void)
{
return IS_ENABLED(CONFIG_KVM_GUEST) && is_kvm_guest();
}
static inline unsigned int kvm_arch_para_features(void)
{
unsigned long r;
if (!kvm_para_available())
return 0;
if(epapr_hypercall0_1(KVM_HCALL_TOKEN(KVM_HC_FEATURES), &r))
return 0;
return r;
}
static inline unsigned int kvm_arch_para_hints(void)
{
return 0;
}
static inline bool kvm_check_and_clear_guest_paused(void)
{
return false;
}
#endif /* __POWERPC_KVM_PARA_H__ */
Annotation
- Immediate include surface: `asm/kvm_guest.h`, `uapi/asm/kvm_para.h`.
- Detected declarations: `function kvm_para_available`, `function kvm_arch_para_features`, `function kvm_arch_para_hints`, `function kvm_check_and_clear_guest_paused`.
- Atlas domain: Architecture Layer / arch/powerpc.
- 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.