kernel/power/em_netlink_autogen.h

File Facts

System

Linux kernel

Corpus path

kernel/power/em_netlink_autogen.h

Extension

.h

Size

883 bytes

Lines

29

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• net/netlink.h
• net/genetlink.h
• uapi/linux/dev_energymodel.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _LINUX_DEV_ENERGYMODEL_GEN_H
#define _LINUX_DEV_ENERGYMODEL_GEN_H

#include <net/netlink.h>
#include <net/genetlink.h>

#include <uapi/linux/dev_energymodel.h>

int dev_energymodel_nl_get_perf_domains_doit(struct sk_buff *skb,
					     struct genl_info *info);
int dev_energymodel_nl_get_perf_domains_dumpit(struct sk_buff *skb,
					       struct netlink_callback *cb);
int dev_energymodel_nl_get_perf_table_doit(struct sk_buff *skb,
					   struct genl_info *info);

enum {
	DEV_ENERGYMODEL_NLGRP_EVENT,
};

extern struct genl_family dev_energymodel_nl_family;

#endif /* _LINUX_DEV_ENERGYMODEL_GEN_H */

Annotation

• Immediate include surface: `net/netlink.h`, `net/genetlink.h`, `uapi/linux/dev_energymodel.h`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.