| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | uncore-power.json | 158 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
166 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
174 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
182 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
190 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
198 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
206 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
214 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
222 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
230 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | uncore-power.json | 158 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
166 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
174 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
182 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
190 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
198 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
206 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
214 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
222 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
230 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | uncore-power.json | 158 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
166 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
174 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
182 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
190 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
198 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
206 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
214 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
222 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
230 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-power.json | 254 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
262 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
270 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
278 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
286 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
294 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
302 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
310 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
318 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
326 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-power.json | 78 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
86 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
94 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
102 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
110 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
118 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
126 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
134 …"PublicDescription": "Counts the number of times when a configurable cores had a C-state demotion",
221 …of threads in C0 to estimate the performance impact that frequency transitions had on the system.",
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | directory-locking.rst | 34 After the locks had been taken, call the method. All locks are exclusive.
85 the order until we had acquired all locks).
114 would have a contended child and we had assumed that no object is its
122 to (2) the order hadn't changed since we had acquired filesystem lock.
135 new parent had been equal to or a descendent of source since the moment when
136 we had acquired filesystem lock and rename() would fail with -ELOOP in that
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | directory-locking.rst | 34 After the locks had been taken, call the method. All locks are exclusive.
85 the order until we had acquired all locks).
114 would have a contended child and we had assumed that no object is its
122 to (2) the order hadn't changed since we had acquired filesystem lock.
135 new parent had been equal to or a descendent of source since the moment when
136 we had acquired filesystem lock and rename() would fail with -ELOOP in that
|
| /kernel/linux/linux-6.6/Documentation/driver-api/usb/ |
| D | persist.rst | 29 though they had disconnected. This is always safe and it is the
39 devices. The effect is exactly the same as if the device really had
40 been unplugged while the system was suspended. If you had a mounted
52 it's as though you had unplugged all the USB devices. Yes, it's
78 reset or otherwise had lost power) then it applies a persistence check
87 kernel treats the device as though it had merely been reset instead of
97 behaves as though the old device had been unplugged and a new device
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | persist.rst | 29 though they had disconnected. This is always safe and it is the
39 devices. The effect is exactly the same as if the device really had
40 been unplugged while the system was suspended. If you had a mounted
52 it's as though you had unplugged all the USB devices. Yes, it's
78 reset or otherwise had lost power) then it applies a persistence check
87 kernel treats the device as though it had merely been reset instead of
97 behaves as though the old device had been unplugged and a new device
|
| /kernel/linux/linux-5.10/Documentation/arm/nwfpe/ |
| D | notes.rst | 16 f4 had been converted to an extended value in the emulator.
18 This is a side effect of the stfe instruction. The double in f4 had to be
19 converted to extended, then stored. If an lfm/sfm combination had been used,
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 16 f4 had been converted to an extended value in the emulator.
18 This is a side effect of the stfe instruction. The double in f4 had to be
19 converted to extended, then stored. If an lfm/sfm combination had been used,
|
| /kernel/linux/linux-5.10/include/net/ |
| D | inet_frag.h | 165 #define IPFRAG_ECN_NOT_ECT 0x01 /* one frag had ECN_NOT_ECT */
166 #define IPFRAG_ECN_ECT_1 0x02 /* one frag had ECN_ECT_1 */
167 #define IPFRAG_ECN_ECT_0 0x04 /* one frag had ECN_ECT_0 */
168 #define IPFRAG_ECN_CE 0x08 /* one frag had ECN_CE */
|
| /kernel/linux/linux-6.6/arch/mips/include/asm/octeon/ |
| D | cvmx-wqe.h | 333 * than allowed and had an FCS error.
338 * and had an FCS error (100M and 10M only).
340 * than allowed and had an FCS error.
341 * - 7 = GMX FCS error: the RGMII packet had an FCS
345 * - 9 = extend error: the RGMII packet had an extend
347 * - 10 = length mismatch error: the RGMII packet had
351 * packet had one or more data reception errors
352 * (RXERR) or the SPI4 packet had one or more
359 * RGMII packet had a studder error (data not
362 * - 16 = FCS error: a SPI4.2 packet had an FCS error.
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-wqe.h | 333 * than allowed and had an FCS error.
338 * and had an FCS error (100M and 10M only).
340 * than allowed and had an FCS error.
341 * - 7 = GMX FCS error: the RGMII packet had an FCS
345 * - 9 = extend error: the RGMII packet had an extend
347 * - 10 = length mismatch error: the RGMII packet had
351 * packet had one or more data reception errors
352 * (RXERR) or the SPI4 packet had one or more
359 * RGMII packet had a studder error (data not
362 * - 16 = FCS error: a SPI4.2 packet had an FCS error.
|
| /kernel/linux/linux-6.6/include/net/ |
| D | inet_frag.h | 175 #define IPFRAG_ECN_NOT_ECT 0x01 /* one frag had ECN_NOT_ECT */
176 #define IPFRAG_ECN_ECT_1 0x02 /* one frag had ECN_ECT_1 */
177 #define IPFRAG_ECN_ECT_0 0x04 /* one frag had ECN_ECT_0 */
178 #define IPFRAG_ECN_CE 0x08 /* one frag had ECN_CE */
|
| /kernel/linux/linux-6.6/Documentation/ABI/removed/ |
| D | video1394 | 7 alternative to raw1394's isochronous I/O functionality which had
8 performance issues in its first generation. Any video1394 user had
|
| /kernel/linux/linux-5.10/Documentation/ABI/removed/ |
| D | video1394 | 7 alternative to raw1394's isochronous I/O functionality which had
8 performance issues in its first generation. Any video1394 user had
|
| /kernel/linux/linux-6.6/fs/btrfs/tests/ |
| D | extent-buffer-tests.c | 19 char *value = "mary had a little lamb"; in test_btrfs_split_item()
20 char *split1 = "mary had a little"; in test_btrfs_split_item()
23 char *split4 = " had a little"; in test_btrfs_split_item()
87 * 'mary had a little' in test_btrfs_split_item()
|
| /kernel/linux/linux-5.10/fs/btrfs/tests/ |
| D | extent-buffer-tests.c | 19 char *value = "mary had a little lamb"; in test_btrfs_split_item()
20 char *split1 = "mary had a little"; in test_btrfs_split_item()
23 char *split4 = " had a little"; in test_btrfs_split_item()
83 * 'mary had a little' in test_btrfs_split_item()
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | biovecs.rst | 53 it had to walk two different bios at the same time, keeping both bi_idx and
61 * Before, any code that might need to use the biovec after the bio had been
63 it somewhere else if there was an error) had to save the entire bvec array
83 bcache) had some ugly workarounds for this.
|
| /kernel/linux/linux-6.6/Documentation/block/ |
| D | biovecs.rst | 55 it had to walk two different bios at the same time, keeping both bi_idx and
63 * Before, any code that might need to use the biovec after the bio had been
65 it somewhere else if there was an error) had to save the entire bvec array
85 bcache) had some ugly workarounds for this.
|
| /kernel/linux/linux-5.10/drivers/block/paride/ |
| D | Transition-notes | 74 from pd.c. That could happen only if pi_do_claimed() had been
86 0 when pd_next_buf() had acquired pd_lock. If it become 0 while
88 the thread that had reset it would be in the area simulateously.
107 check its value is in ps_set_intr() and if it had been non-zero at that
|
| /kernel/linux/linux-5.10/drivers/base/firmware_loader/ |
| D | fallback.h | 16 * as if one had enabled CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y.
20 * This emulates the behaviour as if we had set the kernel
|
| /kernel/linux/linux-6.6/arch/arm64/kvm/hyp/nvhe/ |
| D | tlb.c | 90 * We could do so much better if we had the VA as well. in __kvm_tlb_flush_vmid_ipa()
122 * we had the VA. in __kvm_tlb_flush_vmid_ipa()
142 * We could do so much better if we had the VA as well. in __kvm_tlb_flush_vmid_ipa_nsh()
174 * we had the VA. in __kvm_tlb_flush_vmid_ipa_nsh()
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | stable-api-nonsense.rst | 60 Assuming that we had a stable kernel source interface for the kernel, a
132 which have had to maintain their older USB interfaces over time. This
139 relatively little pain. If Linux had to ensure that it will preserve a
141 the older, broken one would have had to be maintained over time, leading
|