include/linux/hypervisor.h
Source file repositories/reference/linux-study-clean/include/linux/hypervisor.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/hypervisor.h- Extension
.h- Size
- 799 bytes
- Lines
- 47
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
Dependency Surface
asm/jailhouse_para.hasm/x86_init.hlinux/of.h
Detected Declarations
function hypervisor_pin_vcpufunction hypervisor_pin_vcpufunction hypervisor_isolated_pci_functions
Annotated Snippet
#ifndef __LINUX_HYPEVISOR_H
#define __LINUX_HYPEVISOR_H
/*
* Generic Hypervisor support
* Juergen Gross <jgross@suse.com>
*/
#ifdef CONFIG_X86
#include <asm/jailhouse_para.h>
#include <asm/x86_init.h>
static inline void hypervisor_pin_vcpu(int cpu)
{
x86_platform.hyper.pin_vcpu(cpu);
}
#else /* !CONFIG_X86 */
#include <linux/of.h>
static inline void hypervisor_pin_vcpu(int cpu)
{
}
static inline bool jailhouse_paravirt(void)
{
return of_find_compatible_node(NULL, NULL, "jailhouse,cell");
}
#endif /* !CONFIG_X86 */
static inline bool hypervisor_isolated_pci_functions(void)
{
if (IS_ENABLED(CONFIG_S390))
return true;
if (IS_ENABLED(CONFIG_LOONGARCH))
return true;
return jailhouse_paravirt();
}
#endif /* __LINUX_HYPEVISOR_H */
Annotation
- Immediate include surface: `asm/jailhouse_para.h`, `asm/x86_init.h`, `linux/of.h`.
- Detected declarations: `function hypervisor_pin_vcpu`, `function hypervisor_pin_vcpu`, `function hypervisor_isolated_pci_functions`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.