| /kernel/linux/linux-5.10/drivers/iommu/intel/ |
| D | Kconfig | 78 bool "Enable Intel IOMMU scalable mode by default"
81 Selecting this option will enable by default the scalable mode if
82 hardware presents the capability. The scalable mode is defined in
83 VT-d 3.0. The scalable mode capability could be checked by reading
85 is not selected, scalable mode support could also be enabled by
|
| D | pasid.c | 213 /* Free scalable mode PASID directory tables: */ in intel_pasid_free_table()
342 * Setup the DID(Domain Identifier) field (Bit 64~79) of scalable mode
352 * Get domain ID value of a scalable mode PASID entry.
362 * of a scalable mode PASID entry.
371 * Setup the AW(Address Width) field (Bit 2~4) of a scalable mode PASID
382 * of a scalable mode PASID entry.
392 * Disable) field (Bit 1) of a scalable mode PASID entry.
401 * scalable mode PASID entry.
409 * Setup the P(Present) field (Bit 0) of a scalable mode PASID
418 * Setup Page Walk Snoop bit (Bit 87) of a scalable mode PASID
[all …]
|
| D | debugfs.c | 224 * Scalable mode root entry points to upper scalable mode in ctx_tbl_walk()
225 * context table and lower scalable mode context table. Each in ctx_tbl_walk()
226 * scalable mode context table has 128 context entries where as in ctx_tbl_walk()
228 * scalable mode, the context entries for former 128 devices are in ctx_tbl_walk()
229 * in the lower scalable mode context table, while the latter in ctx_tbl_walk()
230 * 128 devices are in the upper scalable mode context table. in ctx_tbl_walk()
231 * In scalable mode, when devfn > 127, iommu_context_addr() in ctx_tbl_walk()
232 * automatically refers to upper scalable mode context table and in ctx_tbl_walk()
234 * between scalable mode and non scalable mode. in ctx_tbl_walk()
|
| /kernel/linux/linux-6.6/drivers/iommu/intel/ |
| D | Kconfig | 87 bool "Enable Intel IOMMU scalable mode by default"
90 Selecting this option will enable by default the scalable mode if
91 hardware presents the capability. The scalable mode is defined in
92 VT-d 3.0. The scalable mode capability could be checked by reading
94 is not selected, scalable mode support could also be enabled by
|
| D | pasid.c | 152 /* Free scalable mode PASID directory tables: */ in intel_pasid_free_table()
281 * Setup the DID(Domain Identifier) field (Bit 64~79) of scalable mode
291 * Get domain ID value of a scalable mode PASID entry.
301 * of a scalable mode PASID entry.
310 * Setup the AW(Address Width) field (Bit 2~4) of a scalable mode PASID
321 * of a scalable mode PASID entry.
331 * Disable) field (Bit 1) of a scalable mode PASID entry.
340 * scalable mode PASID entry.
348 * Setup the P(Present) field (Bit 0) of a scalable mode PASID
357 * Setup Page Walk Snoop bit (Bit 87) of a scalable mode PASID
[all …]
|
| D | debugfs.c | 228 * Scalable mode root entry points to upper scalable mode in ctx_tbl_walk()
229 * context table and lower scalable mode context table. Each in ctx_tbl_walk()
230 * scalable mode context table has 128 context entries where as in ctx_tbl_walk()
232 * scalable mode, the context entries for former 128 devices are in ctx_tbl_walk()
233 * in the lower scalable mode context table, while the latter in ctx_tbl_walk()
234 * 128 devices are in the upper scalable mode context table. in ctx_tbl_walk()
235 * In scalable mode, when devfn > 127, iommu_context_addr() in ctx_tbl_walk()
236 * automatically refers to upper scalable mode context table and in ctx_tbl_walk()
238 * between scalable mode and non scalable mode. in ctx_tbl_walk()
|
| /kernel/linux/linux-6.6/net/ipv4/ |
| D | tcp_scalable.c | 2 /* Tom Kelly's Scalable TCP
4 * See http://www.deneholme.net/tom/scalable/
47 .name = "scalable",
65 MODULE_DESCRIPTION("Scalable TCP");
|
| /kernel/linux/linux-5.10/net/ipv4/ |
| D | tcp_scalable.c | 2 /* Tom Kelly's Scalable TCP
4 * See http://www.deneholme.net/tom/scalable/
47 .name = "scalable",
65 MODULE_DESCRIPTION("Scalable TCP");
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/ |
| D | common-and-microarch.json | 741 "PublicDescription": "Scalable floating-point element Operations speculatively executed.",
744 "BriefDescription": "Scalable floating-point element Operations speculatively executed."
747 … "PublicDescription": "Non-scalable floating-point element Operations speculatively executed.",
750 "BriefDescription": "Non-scalable floating-point element Operations speculatively executed."
753 …"PublicDescription": "Scalable half-precision floating-point element Operations speculatively exec…
756 …"BriefDescription": "Scalable half-precision floating-point element Operations speculatively execu…
759 …"PublicDescription": "Non-scalable half-precision floating-point element Operations speculatively …
762 …"BriefDescription": "Non-scalable half-precision floating-point element Operations speculatively e…
765 …"PublicDescription": "Scalable single-precision floating-point element Operations speculatively ex…
768 …"BriefDescription": "Scalable single-precision floating-point element Operations speculatively exe…
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | voltagedomains54xx_data.c | 35 .scalable = true,
46 .scalable = true,
57 .scalable = true,
|
| D | voltagedomains44xx_data.c | 49 .scalable = true,
60 .scalable = true,
71 .scalable = true,
|
| D | voltage.h | 49 * @scalable: Whether or not this voltage domain is scalable
64 bool scalable; member
|
| D | voltagedomains3xxx_data.c | 50 .scalable = true,
61 .scalable = true,
|
| /kernel/linux/linux-6.6/arch/arm/mach-omap2/ |
| D | voltagedomains54xx_data.c | 35 .scalable = true,
46 .scalable = true,
57 .scalable = true,
|
| D | voltagedomains44xx_data.c | 49 .scalable = true,
60 .scalable = true,
71 .scalable = true,
|
| D | voltage.h | 49 * @scalable: Whether or not this voltage domain is scalable
64 bool scalable; member
|
| D | voltagedomains3xxx_data.c | 50 .scalable = true,
61 .scalable = true,
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | fp_operation.json | 16 …"PublicDescription": "Counts speculatively executed scalable single precision floating point opera…
20 …"PublicDescription": "Counts speculatively executed non-scalable single precision floating point o…
|
| /kernel/linux/linux-5.10/drivers/net/can/mscan/ |
| D | Kconfig | 6 The Motorola Scalable Controller Area Network (MSCAN) definition
8 implementation of the Motorola Scalable CAN concept targeted for
|
| /kernel/linux/linux-6.6/drivers/net/can/mscan/ |
| D | Kconfig | 6 The Motorola Scalable Controller Area Network (MSCAN) definition
8 implementation of the Motorola Scalable CAN concept targeted for
|
| /kernel/linux/linux-6.6/kernel/trace/ |
| D | trace_clock.c | 11 * - medium: scalable global clock with some jitter
37 * sched_clock() is an architecture implemented, fast, scalable, in trace_clock_local()
54 * jitter between CPUs. So it's a pretty scalable clock, but there
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | trace_clock.c | 11 * - medium: scalable global clock with some jitter
37 * sched_clock() is an architecture implemented, fast, scalable, in trace_clock_local()
54 * jitter between CPUs. So it's a pretty scalable clock, but there
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | ceph.rst | 34 system extremely efficient and scalable.
37 in-memory cache above the file namespace that is extremely scalable,
46 independent metadata servers, allowing scalable concurrent access.
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | ceph.rst | 34 system extremely efficient and scalable.
37 in-memory cache above the file namespace that is extremely scalable,
46 independent metadata servers, allowing scalable concurrent access.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | trace_clock.h | 10 * - medium: scalable global clock with some jitter
|