| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | virtual-memory.json | 26 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 35 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 90 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 99 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 154 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 163 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| H A D | other.json | 47 "BriefDescription": "Cycles the uncore cannot take further requests", 52 …umber of cycles when the thread is active and the uncore cannot take any further requests (for exa…
|
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | virtual-memory.json | 26 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 35 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 90 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 99 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 154 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 163 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| H A D | virtual-memory.json | 26 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 35 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 90 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 99 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 154 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 163 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | virtual-memory.json | 26 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 35 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 90 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 99 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 154 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 163 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/skylake/ |
| H A D | virtual-memory.json | 35 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 62 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 126 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 135 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 171 …2M/4M/1G) caused by a code fetch. This implies it missed in the ITLB and further levels of TLB, bu… 198 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | virtual-memory.json | 35 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 62 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 126 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 135 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 171 …2M/4M/1G) caused by a code fetch. This implies it missed in the ITLB and further levels of TLB, bu… 198 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | virtual-memory.json | 35 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 44 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 53 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 62 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 108 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 117 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 126 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 135 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 171 …2M/4M/1G) caused by a code fetch. This implies it missed in the ITLB and further levels of TLB, bu… 198 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | virtual-memory.json | 26 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 35 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 44 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 53 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 90 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 99 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 108 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 117 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 154 "PublicDescription": "Counts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 163 "PublicDescription": "Counts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further level [all...] |
| /linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | virtual-memory.json | 26 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 35 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 44 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 53 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 90 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 99 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 108 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 117 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 154 "PublicDescription": "Counts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 163 "PublicDescription": "Counts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further level [all...] |
| /linux/tools/perf/pmu-events/arch/x86/alderlake/ |
| H A D | virtual-memory.json | 38 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 48 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 58 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 68 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 119 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 129 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 139 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 149 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 218 "PublicDescription": "Counts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 228 "PublicDescription": "Counts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further level [all...] |
| /linux/tools/perf/pmu-events/arch/x86/pantherlake/ |
| H A D | virtual-memory.json | 56 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 66 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 76 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 96 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 166 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 176 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 186 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 206 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 275 "PublicDescription": "Counts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 285 "PublicDescription": "Counts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further level [all...] |
| /linux/crypto/ |
| H A D | Kconfig | 400 for further information. 428 See https://www.schneier.com/blowfish.html for further information. 447 See https://info.isl.ntt.co.jp/crypt/eng/camellia/ for further information. 490 for further information. 505 for further information. 516 See https://www.cl.cam.ac.uk/~rja14/serpent.html for further information. 544 See https://eprint.iacr.org/2008/329.pdf for further information. 578 See https://www.schneier.com/twofish.html for further information. 637 Bernstein and further specified in RFC7539 for use in IETF protocols. 639 https://cr.yp.to/chacha/chacha-20080128.pdf for further information. [all …]
|
| /linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | virtual-memory.json | 26 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 35 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 44 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 53 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 90 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 154 "PublicDescription": "Counts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 163 "PublicDescription": "Counts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 172 "PublicDescription": "Counts completed page walks (4K page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.",
|
| /linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
| H A D | virtual-memory.json | 46 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 56 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 76 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 96 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data loads. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 165 "PublicDescription": "Counts completed page walks (all page sizes) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 175 "PublicDescription": "Counts completed page walks (1G sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 195 "PublicDescription": "Counts completed page walks (2M/4M sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 215 "PublicDescription": "Counts completed page walks (4K sizes) caused by demand data stores. This implies address translations missed in the DTLB and further levels of TLB. The page walk can end with or without a fault.", 294 "PublicDescription": "Counts completed page walks (all page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. The page walk can end with or without a fault.", 314 "PublicDescription": "Counts completed page walks (2M/4M page sizes) caused by a code fetch. This implies it missed in the ITLB (Instruction TLB) and further level [all...] |
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | blkio-controller.rst | 152 are further divided by the type of operation - read or write, sync 159 are further divided by the type of operation - read or write, sync 172 io_service_time > actual time elapsed. This time is further divided by 188 devices too. This time is further divided by the type of operation - 195 cgroup. This is further divided by the type of operation - read or 200 cgroup. This is further divided by the type of operation - read or 285 are further divided by the type of operation - read or write, sync 292 are further divided by the type of operation - read or write, sync
|
| /linux/tools/perf/pmu-events/arch/x86/lunarlake/ |
| H A D | virtual-memory.json | 65 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 75 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 95 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 115 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 204 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 214 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 234 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 254 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 352 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 372 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
| /linux/drivers/net/wireless/silabs/wfx/ |
| H A D | Kconfig | 3 tristate "Silicon Labs wireless chips WF200 and further" 8 This is a driver for Silicons Labs WFxxx series (WF200 and further)
|
| /linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 18 which need further coordination. 100 response team can bring in further developers (domain experts) to address 137 further disclosure, and coordination of fixes. 175 a sufficient starting point, and further technical clarification is best 195 The initial response team will identify further experts from the Linux 197 further experts to be included, each of which will be subject to the same 285 reporting process and further handling. Ambassadors are not involved in the
|
| /linux/drivers/net/ethernet/hisilicon/ |
| H A D | Kconfig | 81 Hi1610 and further ICT SoC 112 SoCs and further upcoming SoCs. 130 SoCs and further upcoming SoCs.
|
| /linux/Documentation/virt/coco/ |
| H A D | sev-guest.rst | 101 specification for further details. 115 SEV-SNP firmware to derive the key. See SEV-SNP specification for further details 119 the SEV-SNP specification for further details. 142 See GHCB specification for further detail on how to parse the certificate blob. 153 specification for further details.
|
| /linux/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 23 internal resource leak thus stopping further packet processing. 28 stall further packet processing. The issue can occur with any
|
| /linux/scripts/kconfig/tests/preprocess/escape/ |
| H A D | Kconfig | 23 # The following should print "$(X)". It should not be expanded further. 33 # The following should print "$(X)". It should not be expanded further.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2-selection-flags.rst | 47 - The configuration must not be propagated to any further processing 49 inside the subdevice to all further processing steps.
|
| /linux/drivers/net/ethernet/sfc/siena/ |
| H A D | tx.h | 24 * packet, it must be one of them; no further checking required. in efx_tx_csum_type_skb() 36 * so it must be one of them. No need for further checks. in efx_tx_csum_type_skb()
|