arch/mips/cavium-octeon/executive/cvmx-sysinfo.c
Source file repositories/reference/linux-study-clean/arch/mips/cavium-octeon/executive/cvmx-sysinfo.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/cavium-octeon/executive/cvmx-sysinfo.c- Extension
.c- Size
- 1798 bytes
- Lines
- 54
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/export.hasm/octeon/cvmx.hasm/octeon/cvmx-sysinfo.h
Detected Declarations
export cvmx_sysinfo_get
Annotated Snippet
#include <linux/export.h>
#include <asm/octeon/cvmx.h>
#include <asm/octeon/cvmx-sysinfo.h>
/*
* This structure defines the private state maintained by sysinfo module.
*/
static struct cvmx_sysinfo sysinfo; /* system information */
/*
* Returns the application information as obtained
* by the bootloader. This provides the core mask of the cores
* running the same application image, as well as the physical
* memory regions available to the core.
*/
struct cvmx_sysinfo *cvmx_sysinfo_get(void)
{
return &sysinfo;
}
EXPORT_SYMBOL(cvmx_sysinfo_get);
Annotation
- Immediate include surface: `linux/export.h`, `asm/octeon/cvmx.h`, `asm/octeon/cvmx-sysinfo.h`.
- Detected declarations: `export cvmx_sysinfo_get`.
- Atlas domain: Architecture Layer / arch/mips.
- Implementation status: integration 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.