| /kernel/linux/linux-5.10/drivers/staging/comedi/drivers/ |
| D | ni_routes.h | 80 struct ni_route_tables *tables);
109 * @tables: pointer to relevant set of routing tables.
134 const struct ni_route_tables *tables);
147 * @tables: pointer to relevant set of routing tables.
152 const struct ni_route_tables *tables);
159 * @tables: pointer to relevant set of routing tables.
164 const struct ni_route_tables *tables) in route_is_valid() argument
166 return ni_route_to_register(src, dest, tables) >= 0; in route_is_valid()
194 * @tables: Routing tables for which to count all valid routes.
196 unsigned int ni_count_valid_routes(const struct ni_route_tables *tables);
[all …]
|
| D | ni_routes.c | 90 * Find the proper route_values and ni_device_routes tables for this particular
99 struct ni_route_tables *tables) in ni_find_device_routes() argument
112 tables->route_values = rv; in ni_find_device_routes()
113 tables->valid_routes = dr; in ni_find_device_routes()
127 * @tables: Pointer to assigned routing information.
141 struct ni_route_tables *tables) in ni_assign_device_routes() argument
143 memset(tables, 0, sizeof(struct ni_route_tables)); in ni_assign_device_routes()
145 tables); in ni_assign_device_routes()
151 * @tables: Routing tables for which to count all valid routes.
153 unsigned int ni_count_valid_routes(const struct ni_route_tables *tables) in ni_count_valid_routes() argument
[all …]
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | initrd_table_override.txt | 1 Upgrading ACPI tables via initrd
13 upgrade the ACPI execution environment that is defined by the ACPI tables
14 via upgrading the ACPI tables provided by the BIOS with an instrumented,
15 modified, more recent version one, or installing brand new ACPI tables.
17 For a full list of ACPI tables that can be upgraded/installed, take a look
19 drivers/acpi/tables.c.
20 All ACPI tables iasl (Intel's ACPI compiler and disassembler) knows should
32 allows you to upgrade the buggy tables before your platform/BIOS vendor
40 platform provided ACPI tables or inserting new ACPI tables.
49 # Extract the machine's ACPI tables:
[all …]
|
| D | acpi-lid.txt | 10 control method lid device. To implement this, the AML tables issue
25 However the word of "current" has ambiguity, some buggy AML tables return
29 initial returning value. When the AML tables implement this control method
35 There are buggy AML tables never notifying when the lid device state is
37 it is guaranteed that the AML tables always notify "closed" when the lid
40 tested, it is reliable from all AML tables.
71 isn't ready to handle the buggy AML tables.
90 opens given that some AML tables do not send "opened" notifications
96 handle the buggy AML tables.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 4 Upgrading ACPI tables via initrd
11 upgrade the ACPI execution environment that is defined by the ACPI tables
12 via upgrading the ACPI tables provided by the BIOS with an instrumented,
13 modified, more recent version one, or installing brand new ACPI tables.
19 For a full list of ACPI tables that can be upgraded/installed, take a look
21 drivers/acpi/tables.c.
23 All ACPI tables iasl (Intel's ACPI compiler and disassembler) knows should
37 allows you to upgrade the buggy tables before your platform/BIOS vendor
45 platform provided ACPI tables or inserting new ACPI tables.
55 # Extract the machine's ACPI tables:
[all …]
|
| /kernel/linux/linux-5.10/scripts/ |
| D | check-sysctl-docs | 95 # Stage 2: process each file and find all sysctl tables
107 match($0, /static struct ctl_path ([^][]+)/, tables)
108 curpath = tables[1]
113 match($0, /static struct ctl_table ([^][]+)/, tables)
114 curtable = tables[1]
150 match($0, /register_sysctl_table\(([^)]+)\)/, tables)
151 if (debug) print "Registering table " tables[1]
152 if (children[tables[1]][table]) {
153 for (entry in entries[children[tables[1]][table]]) {
160 match($0, /register_sysctl_paths\(([^)]+), ([^)]+)\)/, tables)
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/util/scripting-engines/ |
| D | trace-event-python.c | 102 struct tables { struct
120 static struct tables tables_global; argument
981 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_evsel() local
989 call_object(tables->evsel_handler, t, "evsel_table"); in python_export_evsel()
999 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_machine() local
1008 call_object(tables->machine_handler, t, "machine_table"); in python_export_machine()
1018 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_thread() local
1029 call_object(tables->thread_handler, t, "thread_table"); in python_export_thread()
1039 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_comm() local
1050 call_object(tables->comm_handler, t, "comm_table"); in python_export_comm()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| D | intel_mpx.txt | 40 the bounds tables between the time when it populates "bndcfgu" and
61 tables. If an entire table becomes unused, we will attempt to free
83 * Frees unused bounds tables at the time that the memory they described
95 * new bounds tables (BT) need to be allocated to save bounds.
100 On-demand kernel allocation of bounds tables
107 tables".
111 hardware during both bounds violations or when the tables are not
112 present. The kernel handles those #BR exceptions for not-present tables
116 The tables need to be accessed and controlled by userspace because
120 tables would obviously destroy performance.
[all …]
|
| D | pti.txt | 9 page tables for use only when running userspace applications. When
11 page tables are switched to the full "kernel" copy. When the system
14 The userspace page tables contain only a minimal amount of kernel
30 When PTI is enabled, the kernel manages two sets of page tables.
35 Although _complete_, the user portion of the kernel page tables is
40 The userspace page tables map only the kernel data needed to enter
46 page tables like normal. The only difference is when the kernel
49 userspace page tables' PGD.
52 layers of the page tables. This leaves a single, shared set of
53 userspace page tables to manage. One PTE to lock, one set of
[all …]
|
| /kernel/linux/linux-4.19/security/apparmor/include/ |
| D | match.h | 25 * The format used for transition tables is based on the GNU flex table
26 * file format (--tables-file option; see Table File Format in the flex
29 * new tables have been defined and others YY_ID_CHK (check) and YY_ID_DEF
30 * (default) tables are used slightly differently (see the apparmor-parser
34 * The data in the packed dfa is stored in network byte order, and the tables
39 * tables.
73 /* ACCEPT & ACCEPT2 tables gets 6 dedicated flags, YYTD_DATAX define the
90 #define DEFAULT_TABLE(DFA) ((u16 *)((DFA)->tables[YYTD_ID_DEF]->td_data))
91 #define BASE_TABLE(DFA) ((u32 *)((DFA)->tables[YYTD_ID_BASE]->td_data))
92 #define NEXT_TABLE(DFA) ((u16 *)((DFA)->tables[YYTD_ID_NXT]->td_data))
[all …]
|
| /kernel/linux/linux-5.10/security/apparmor/include/ |
| D | match.h | 21 * The format used for transition tables is based on the GNU flex table
22 * file format (--tables-file option; see Table File Format in the flex
25 * new tables have been defined and others YY_ID_CHK (check) and YY_ID_DEF
26 * (default) tables are used slightly differently (see the apparmor-parser
30 * The data in the packed dfa is stored in network byte order, and the tables
35 * tables.
73 /* ACCEPT & ACCEPT2 tables gets 6 dedicated flags, YYTD_DATAX define the
90 #define DEFAULT_TABLE(DFA) ((u16 *)((DFA)->tables[YYTD_ID_DEF]->td_data))
91 #define BASE_TABLE(DFA) ((u32 *)((DFA)->tables[YYTD_ID_BASE]->td_data))
92 #define NEXT_TABLE(DFA) ((u16 *)((DFA)->tables[YYTD_ID_NXT]->td_data))
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/util/scripting-engines/ |
| D | trace-event-python.c | 100 struct tables { struct
116 static struct tables tables_global; argument
950 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_evsel() local
958 call_object(tables->evsel_handler, t, "evsel_table"); in python_export_evsel()
968 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_machine() local
977 call_object(tables->machine_handler, t, "machine_table"); in python_export_machine()
987 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_thread() local
998 call_object(tables->thread_handler, t, "thread_table"); in python_export_thread()
1007 struct tables *tables = container_of(dbe, struct tables, dbe); in python_export_comm() local
1015 call_object(tables->comm_handler, t, "comm_table"); in python_export_comm()
[all …]
|
| /kernel/linux/linux-4.19/security/apparmor/ |
| D | match.c | 127 /* if table was vmalloced make sure the page tables are synced in unpack_table()
142 * verify_table_headers - verify that the tables headers are as expected
143 * @tables - array of dfa tables to check (NOT NULL)
151 static int verify_table_headers(struct table_header **tables, int flags) in verify_table_headers() argument
156 /* check that required tables exist */ in verify_table_headers()
157 if (!(tables[YYTD_ID_DEF] && tables[YYTD_ID_BASE] && in verify_table_headers()
158 tables[YYTD_ID_NXT] && tables[YYTD_ID_CHK])) in verify_table_headers()
162 state_count = tables[YYTD_ID_BASE]->td_lolen; in verify_table_headers()
164 if (!tables[YYTD_ID_ACCEPT]) in verify_table_headers()
166 if (state_count != tables[YYTD_ID_ACCEPT]->td_lolen) in verify_table_headers()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | pti.rst | 15 page tables for use only when running userspace applications. When
17 page tables are switched to the full "kernel" copy. When the system
20 The userspace page tables contain only a minimal amount of kernel
36 When PTI is enabled, the kernel manages two sets of page tables.
41 Although _complete_, the user portion of the kernel page tables is
46 The userspace page tables map only the kernel data needed to enter
52 page tables like normal. The only difference is when the kernel
55 userspace page tables' PGD.
58 layers of the page tables. This leaves a single, shared set of
59 userspace page tables to manage. One PTE to lock, one set of
[all …]
|
| /kernel/linux/linux-5.10/security/apparmor/ |
| D | match.c | 123 /* if table was vmalloced make sure the page tables are synced in unpack_table()
138 * verify_table_headers - verify that the tables headers are as expected
139 * @tables - array of dfa tables to check (NOT NULL)
147 static int verify_table_headers(struct table_header **tables, int flags) in verify_table_headers() argument
152 /* check that required tables exist */ in verify_table_headers()
153 if (!(tables[YYTD_ID_DEF] && tables[YYTD_ID_BASE] && in verify_table_headers()
154 tables[YYTD_ID_NXT] && tables[YYTD_ID_CHK])) in verify_table_headers()
158 state_count = tables[YYTD_ID_BASE]->td_lolen; in verify_table_headers()
160 if (!tables[YYTD_ID_ACCEPT]) in verify_table_headers()
162 if (state_count != tables[YYTD_ID_ACCEPT]->td_lolen) in verify_table_headers()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-tables | 1 What: /sys/firmware/dmi/tables/
13 The dmi/tables provides raw SMBIOS entry point and DMI tables
18 /sys/firmware/dmi/tables/smbios_entry_point
19 /sys/firmware/dmi/tables/DMI
22 tables.
|
| D | sysfs-firmware-sfi | 1 What: /sys/firmware/sfi/tables/
5 SFI defines a number of small static memory tables
8 The tables are defined in the latest SFI specification:
11 While the tables are used by the kernel, user-space
14 # cd /sys/firmware/sfi/tables
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-tables | 1 What: /sys/firmware/dmi/tables/
13 The dmi/tables provides raw SMBIOS entry point and DMI tables
18 /sys/firmware/dmi/tables/smbios_entry_point
19 /sys/firmware/dmi/tables/DMI
22 tables.
|
| D | sysfs-firmware-sfi | 1 What: /sys/firmware/sfi/tables/
5 SFI defines a number of small static memory tables
8 The tables are defined in the latest SFI specification:
11 While the tables are used by the kernel, user-space
14 # cd /sys/firmware/sfi/tables
|
| /kernel/linux/linux-5.10/tools/power/acpi/man/ |
| D | acpidump.8 | 3 acpidump \- dump a system's ACPI tables to an ASCII file
12 dumps the systems ACPI tables to an ASCII file appropriate for
23 Dump tables to binary files
32 Dump tables from specified RSDP
64 Invocation without parameters dumps all available tables.
106 /sys/firmware/acpi/tables/*
107 /sys/firmware/acpi/tables/dynamic/*
|
| /kernel/linux/linux-4.19/tools/power/acpi/man/ |
| D | acpidump.8 | 3 acpidump \- dump a system's ACPI tables to an ASCII file
12 dumps the systems ACPI tables to an ASCII file appropriate for
23 Dump tables to binary files
32 Dump tables from specified RSDP
64 Invocation without parameters dumps all available tables.
106 /sys/firmware/acpi/tables/*
107 /sys/firmware/acpi/tables/dynamic/*
|
| /kernel/linux/linux-4.19/Documentation/crypto/ |
| D | descore-readme.txt | 50 30us per encryption (options: 64k tables, no IP/FP)
51 33us per encryption (options: 64k tables, FIPS standard bit ordering)
52 45us per encryption (options: 2k tables, no IP/FP)
53 48us per encryption (options: 2k tables, FIPS standard bit ordering)
54 275us to set a new key (uses 1k of key tables)
66 53us per encryption (uses 2k of tables)
67 96us to set a new key (uses 2.25k of key tables)
84 68us per encryption (uses 2k of tables)
85 96us to set a new key (uses 2.25k of key tables)
101 he claims to use 280k of tables but the iteration calculation seems
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-emc.txt | 11 set of tables can be present and said tables will be used
33 and the tables are stored directly under the emc node (see below).
37 - name : Should be emc-tables
49 There are two ways of specifying which tables to use:
51 * The simplest is if there is just one set of tables in the device tree,
62 used to select which tables to use.
67 - reg : either an opaque enumerator to tell different tables apart, or
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-emc.txt | 11 set of tables can be present and said tables will be used
37 and the tables are stored directly under the emc node (see below).
41 - name : Should be emc-tables
53 There are two ways of specifying which tables to use:
55 * The simplest is if there is just one set of tables in the device tree,
66 used to select which tables to use.
71 - reg : either an opaque enumerator to tell different tables apart, or
|
| /kernel/linux/linux-5.10/Documentation/crypto/ |
| D | descore-readme.rst | 62 - 30us per encryption (options: 64k tables, no IP/FP)
63 - 33us per encryption (options: 64k tables, FIPS standard bit ordering)
64 - 45us per encryption (options: 2k tables, no IP/FP)
65 - 48us per encryption (options: 2k tables, FIPS standard bit ordering)
66 - 275us to set a new key (uses 1k of key tables)
80 - 53us per encryption (uses 2k of tables)
81 - 96us to set a new key (uses 2.25k of key tables)
106 - 68us per encryption (uses 2k of tables)
107 - 96us to set a new key (uses 2.25k of key tables)
126 he claims to use 280k of tables but the iteration calculation seems
[all …]
|