tools/include/nolibc/sched.h
Source file repositories/reference/linux-study-clean/tools/include/nolibc/sched.h
File Facts
- System
- Linux kernel
- Corpus path
tools/include/nolibc/sched.h- Extension
.h- Size
- 866 bytes
- Lines
- 51
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
nolibc.hsys.hlinux/sched.h
Detected Declarations
function __attribute__function __attribute__function __attribute__function __attribute__
Annotated Snippet
#include "nolibc.h"
#ifndef _NOLIBC_SCHED_H
#define _NOLIBC_SCHED_H
#include "sys.h"
#include <linux/sched.h>
/*
* int setns(int fd, int nstype);
*/
static __attribute__((unused))
int _sys_setns(int fd, int nstype)
{
return __nolibc_syscall2(__NR_setns, fd, nstype);
}
static __attribute__((unused))
int setns(int fd, int nstype)
{
return __sysret(_sys_setns(fd, nstype));
}
/*
* int unshare(int flags);
*/
static __attribute__((unused))
int _sys_unshare(int flags)
{
return __nolibc_syscall1(__NR_unshare, flags);
}
static __attribute__((unused))
int unshare(int flags)
{
return __sysret(_sys_unshare(flags));
}
#endif /* _NOLIBC_SCHED_H */
Annotation
- Immediate include surface: `nolibc.h`, `sys.h`, `linux/sched.h`.
- Detected declarations: `function __attribute__`, `function __attribute__`, `function __attribute__`, `function __attribute__`.
- Atlas domain: Support Tooling And Documentation / tools.
- 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.