include/linux/psp.h
Source file repositories/reference/linux-study-clean/include/linux/psp.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/psp.h- Extension
.h- Size
- 771 bytes
- Lines
- 31
- 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
linux/mem_encrypt.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __PSP_H
#define __PSP_H
#ifdef CONFIG_X86
#include <linux/mem_encrypt.h>
#define __psp_pa(x) __sme_pa(x)
#else
#define __psp_pa(x) __pa(x)
#endif
/*
* Fields and bits used by most PSP mailboxes
*
* Note: Some mailboxes (such as SEV) have extra bits or different meanings
* and should include an appropriate local definition in their source file.
*/
#define PSP_CMDRESP_STS GENMASK(15, 0)
#define PSP_TEE_STS_RING_BUSY 0x0000000d /* Ring already initialized */
#define PSP_CMDRESP_CMD GENMASK(23, 16)
#define PSP_CMDRESP_RESERVED GENMASK(29, 24)
#define PSP_CMDRESP_RECOVERY BIT(30)
#define PSP_CMDRESP_RESP BIT(31)
#define PSP_DRBL_MSG PSP_CMDRESP_CMD
#define PSP_DRBL_RING BIT(0)
#endif /* __PSP_H */
Annotation
- Immediate include surface: `linux/mem_encrypt.h`.
- 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.