| /linux/drivers/iommu/intel/ |
| H A D | pasid.h | 126 * Setup the DID(Domain Identifier) field (Bit 64~79) of scalable mode 136 * Get domain ID value of a scalable mode PASID entry. 146 * of a scalable mode PASID entry. 155 * Setup the AW(Address Width) field (Bit 2~4) of a scalable mode PASID 166 * of a scalable mode PASID entry. 176 * Disable) field (Bit 1) of a scalable mode PASID entry. 185 * Access Dirty Enable) field (Bit 9) of a scalable mode PASID 195 * Access Dirty Enable) field (Bit 9) of a scalable mode PASID 205 * Access Dirty Enable) field (Bit 9) of a scalable mode PASID 215 * scalable mode PASID entry. [all …]
|
| H A D | Kconfig | 81 bool "Enable Intel IOMMU scalable mode by default" 84 Selecting this option will enable by default the scalable mode if 85 hardware presents the capability. The scalable mode is defined in 86 VT-d 3.0. The scalable mode capability could be checked by reading 88 is not selected, scalable mode support could also be enabled by
|
| H A D | pasid.c | 95 /* Free scalable mode PASID directory tables: */ in intel_pasid_free_table() 346 * Set up the scalable mode pasid table entry for first only 460 * Set up the scalable mode pasid entry for second only translation type. 640 * Set up the scalable mode pasid entry for passthrough translation type. 911 * Interfaces to setup or teardown a pasid table to the scalable-mode 959 * Get the PASID directory size for scalable mode context entry. 960 * Value of X in the PDTS field of a scalable mode context entry 1122 * IOMMU is in scalable mode but all PASID table entries of the device are 1133 * when operating in scalable mode. Therefore the @did value doesn't in intel_context_flush_no_pasid() 1134 * matter in scalable mode. in intel_context_flush_no_pasid()
|
| /linux/net/ipv4/ |
| H A 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");
|
| /linux/tools/perf/pmu-events/arch/arm64/ |
| H A D | common-and-microarch.json | 1141 "PublicDescription": "Scalable floating-point element Operations speculatively executed.", 1144 "BriefDescription": "Scalable floating-point element Operations speculatively executed." 1147 … "PublicDescription": "Non-scalable floating-point element Operations speculatively executed.", 1150 "BriefDescription": "Non-scalable floating-point element Operations speculatively executed." 1153 …"PublicDescription": "Scalable half-precision floating-point element Operations speculatively exec… 1156 …"BriefDescription": "Scalable half-precision floating-point element Operations speculatively execu… 1159 …"PublicDescription": "Non-scalable half-precision floating-point element Operations speculatively … 1162 …"BriefDescription": "Non-scalable half-precision floating-point element Operations speculatively e… 1165 …"PublicDescription": "Scalable single-precision floating-point element Operations speculatively ex… 1168 …"BriefDescription": "Scalable single-precision floating-point element Operations speculatively exe… [all …]
|
| /linux/arch/arm/mach-omap2/ |
| H A D | voltagedomains54xx_data.c | 35 .scalable = true, 46 .scalable = true, 57 .scalable = true,
|
| H A D | voltagedomains44xx_data.c | 49 .scalable = true, 60 .scalable = true, 71 .scalable = true,
|
| H A D | voltage.h | 49 * @scalable: Whether or not this voltage domain is scalable 64 bool scalable; member
|
| H A D | voltagedomains3xxx_data.c | 50 .scalable = true, 61 .scalable = true,
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ |
| H A D | fp_operation.json | 4 …"PublicDescription": "Counts speculatively executed scalable single precision floating point opera… 8 …"PublicDescription": "Counts speculatively executed non-scalable single precision floating point o…
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| H A 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…
|
| /linux/drivers/net/can/mscan/ |
| H A D | Kconfig | 6 The Motorola Scalable Controller Area Network (MSCAN) definition 8 implementation of the Motorola Scalable CAN concept targeted for
|
| /linux/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/ |
| H A D | fp_operation.json | 251 …"BriefDescription": "This event counts architecturally executed non-scalable element arithmetic op… 255 …"BriefDescription": "This event counts architecturally executed non-scalable element arithmetic op… 259 …"BriefDescription": "This event counts architecturally executed scalable element arithmetic operat… 263 …"BriefDescription": "This event counts architecturally executed scalable element arithmetic operat…
|
| /linux/kernel/trace/ |
| H A 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
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-intel-iommu | 227 in legacy mode or scalable mode. 234 For a device that supports scalable mode, dump the 261 supports scalable mode.
|
| /linux/include/linux/ |
| H A D | trace_clock.h | 10 * - medium: scalable global clock with some jitter
|
| H A D | sbitmap.h | 3 * Fast and scalable bitmaps. 47 * struct sbitmap - Scalable bitmap. 101 * struct sbitmap_queue - Scalable bitmap with the added ability to wait on free 111 * @sb: Scalable bitmap.
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | mstar,msc313-cpupll.yaml | 13 The MStar/SigmaStar MSC313 and later ARMv7 chips have a scalable
|
| /linux/fs/ceph/ |
| H A D | Kconfig | 12 scalable file system designed to provide high performance,
|
| /linux/Documentation/arch/x86/ |
| H A D | sva.rst | 34 Unlike Single Root I/O Virtualization (SR-IOV), Scalable IOV (SIOV) permits 224 Scalable I/O Virtualization builds on the PASID concept to create device 280 https://01.org/blogs/2019/assignable-interfaces-intel-scalable-i/o-virtualization-linux
|
| /linux/Documentation/mm/ |
| H A D | numa.rst | 38 lives interesting. Rather, this architecture is a means to provide scalable 39 memory bandwidth. However, to achieve scalable memory bandwidth, system and
|
| /linux/Documentation/driver-api/crypto/iaa/ |
| H A D | iaa-crypto.rst | 78 - Scalable 83 Scalable mode 86 Scalable mode supports Shared Virtual Memory (SVM or SVA). It is 93 With scalable mode, both shared and dedicated workqueues are available 96 For scalable mode, the following BIOS settings should be enabled::
|
| /linux/drivers/block/ |
| H A D | rbd_types.h | 2 * Ceph - scalable distributed file system
|
| /linux/Documentation/mm/damon/ |
| H A D | index.rst | 15 - *scalable* (the upper-bound of the overhead is in constant range regardless
|
| /linux/arch/arm64/include/asm/ |
| H A D | fpsimdmacros.h | 80 .error "Bad Scalable Vector Extension vector register number \znr." 86 .error "Bad Scalable Vector Extension predicate register number \pnr."
|