arch/x86/xen/suspend_hvm.c
Source file repositories/reference/linux-study-clean/arch/x86/xen/suspend_hvm.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/xen/suspend_hvm.c- Extension
.c- Size
- 537 bytes
- Lines
- 28
- Domain
- Architecture Layer
- Bucket
- arch/x86
- 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
linux/types.hxen/xen.hxen/hvm.hxen/features.hxen/interface/features.hxen/events.hxen-ops.h
Detected Declarations
function xen_hvm_post_suspend
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include <linux/types.h>
#include <xen/xen.h>
#include <xen/hvm.h>
#include <xen/features.h>
#include <xen/interface/features.h>
#include <xen/events.h>
#include "xen-ops.h"
void xen_hvm_post_suspend(int suspend_cancelled)
{
if (!suspend_cancelled) {
xen_hvm_init_shared_info();
xen_vcpu_restore();
}
if (xen_percpu_upcall) {
unsigned int cpu;
for_each_online_cpu(cpu)
BUG_ON(xen_set_upcall_vector(cpu));
} else {
xen_setup_callback_vector();
}
xen_unplug_emulated_devices();
}
Annotation
- Immediate include surface: `linux/types.h`, `xen/xen.h`, `xen/hvm.h`, `xen/features.h`, `xen/interface/features.h`, `xen/events.h`, `xen-ops.h`.
- Detected declarations: `function xen_hvm_post_suspend`.
- Atlas domain: Architecture Layer / arch/x86.
- 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.