arch/arm/xen/grant-table.c
Source file repositories/reference/linux-study-clean/arch/arm/xen/grant-table.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/xen/grant-table.c- Extension
.c- Size
- 2114 bytes
- Lines
- 59
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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
xen/interface/xen.hxen/page.hxen/grant_table.h
Detected Declarations
function filefunction arch_gnttab_unmapfunction arch_gnttab_map_statusfunction arch_gnttab_init
Annotated Snippet
#include <xen/interface/xen.h>
#include <xen/page.h>
#include <xen/grant_table.h>
int arch_gnttab_map_shared(xen_pfn_t *frames, unsigned long nr_gframes,
unsigned long max_nr_gframes,
void **__shared)
{
return -ENOSYS;
}
void arch_gnttab_unmap(void *shared, unsigned long nr_gframes)
{
return;
}
int arch_gnttab_map_status(uint64_t *frames, unsigned long nr_gframes,
unsigned long max_nr_gframes,
grant_status_t **__shared)
{
return -ENOSYS;
}
int arch_gnttab_init(unsigned long nr_shared, unsigned long nr_status)
{
return 0;
}
Annotation
- Immediate include surface: `xen/interface/xen.h`, `xen/page.h`, `xen/grant_table.h`.
- Detected declarations: `function file`, `function arch_gnttab_unmap`, `function arch_gnttab_map_status`, `function arch_gnttab_init`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.