every (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:every (Results 1 – 25 of 4131) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...166

/kernel/linux/linux-4.19/drivers/thunderbolt/
D	nhi_regs.h	`39 * 16 bytes per entry, one entry for every hop (REG_HOP_COUNT) 48 * 16 bytes per entry, one entry for every hop (REG_HOP_COUNT) 58 * 32 bytes per entry, one entry for every hop (REG_HOP_COUNT) 66 * 32 bytes per entry, one entry for every hop (REG_HOP_COUNT) 79 * Every bitfield contains one bit for every hop (REG_HOP_COUNT). Registers are 88 * Both bitfields contains one bit for every hop (REG_HOP_COUNT). To`
/kernel/linux/linux-5.10/drivers/thunderbolt/
D	nhi_regs.h	`40 * 16 bytes per entry, one entry for every hop (REG_HOP_COUNT) 49 * 16 bytes per entry, one entry for every hop (REG_HOP_COUNT) 59 * 32 bytes per entry, one entry for every hop (REG_HOP_COUNT) 67 * 32 bytes per entry, one entry for every hop (REG_HOP_COUNT) 80 * Every bitfield contains one bit for every hop (REG_HOP_COUNT). Registers are 89 * Both bitfields contains one bit for every hop (REG_HOP_COUNT). To`
/kernel/linux/linux-4.19/Documentation/vm/
D	frontswap.rst	138 If CONFIG_FRONTSWAP is disabled, every frontswap hook compiles into 142 every swap page read or written. If CONFIG_FRONTSWAP is enabled 143 AND a frontswap backend registers AND the backend fails every "store" 145 CPU overhead is still negligible -- and since every frontswap fail 151 registers, one bit is allocated for every swap page for every swap 154 for every swap page for every swap device that is swapon'd. (Hugh 186 page, it could accept every ninth page, or it might accept every 201 So every time the frontswap backend accepts a page, a swap device read 249 implemented as a "shadow" to every swapon'd device with the potential 250 capability of holding every page that the swap device might have held
/kernel/linux/linux-5.10/Documentation/vm/
D	frontswap.rst	138 If CONFIG_FRONTSWAP is disabled, every frontswap hook compiles into 142 every swap page read or written. If CONFIG_FRONTSWAP is enabled 143 AND a frontswap backend registers AND the backend fails every "store" 145 CPU overhead is still negligible -- and since every frontswap fail 151 registers, one bit is allocated for every swap page for every swap 154 for every swap page for every swap device that is swapon'd. (Hugh 186 page, it could accept every ninth page, or it might accept every 201 So every time the frontswap backend accepts a page, a swap device read 249 implemented as a "shadow" to every swapon'd device with the potential 250 capability of holding every page that the swap device might have held
/kernel/linux/linux-4.19/Documentation/PCI/endpoint/
D	pci-endpoint-cfs.txt	`19 functions. Every EPC device present in the system will have an entry in 20 the controllers directory and and every EPF driver present in the system 29 Every registered EPF driver will be listed in controllers directory. The 43 Every <EPF device> directory consists of the following entries that can be 63 Every registered EPC device will be listed in controllers directory. The`
/kernel/linux/linux-5.10/arch/mips/include/asm/octeon/
D	cvmx-helper-board.h	`66 * This function must be modifed for every new Octeon board. 69 * fact that every Octeon board receives a unique board type 84 * This function must be modifed for every new Octeon board. 87 * fact that every Octeon board receives a unique board type 106 * This function must be modifed for every new Octeon board. 109 * fact that every Octeon board receives a unique board type`
/kernel/linux/linux-4.19/arch/mips/include/asm/octeon/
D	cvmx-helper-board.h	`66 * This function must be modifed for every new Octeon board. 69 * fact that every Octeon board receives a unique board type 84 * This function must be modifed for every new Octeon board. 87 * fact that every Octeon board receives a unique board type 106 * This function must be modifed for every new Octeon board. 109 * fact that every Octeon board receives a unique board type`
/kernel/linux/linux-5.10/Documentation/ABI/testing/
D	sysfs-bus-rpmsg	`6 Every rpmsg device is a communication channel with a remote 18 Every rpmsg device is a communication channel with a remote 36 Every rpmsg device is a communication channel with a remote 58 Every rpmsg device is a communication channel with a remote 82 Every rpmsg device is a communication channel with a remote`
/kernel/linux/linux-4.19/Documentation/ABI/testing/
D	sysfs-bus-rpmsg	`6 Every rpmsg device is a communication channel with a remote 18 Every rpmsg device is a communication channel with a remote 36 Every rpmsg device is a communication channel with a remote 58 Every rpmsg device is a communication channel with a remote 82 Every rpmsg device is a communication channel with a remote`
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/
D	uncore-other.json	578 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 590 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 602 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 614 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 626 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 638 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 650 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 662 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 722 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO … 734 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO … [all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/
D	uncore-other.json	557 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 569 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 581 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 593 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 605 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 617 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 629 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 641 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 701 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO … 713 …"PublicDescription": "Counts every peer to peer write request of 4 bytes of data made to the MMIO … [all …]
/kernel/linux/linux-5.10/Documentation/PCI/endpoint/
D	pci-endpoint-cfs.rst	`26 functions. Every EPC device present in the system will have an entry in 27 the controllers directory and every EPF driver present in the system 38 Every registered EPF driver will be listed in controllers directory. The 53 Every <EPF device> directory consists of the following entries that can be 75 Every registered EPC device will be listed in controllers directory. The`
/kernel/linux/linux-4.19/Documentation/admin-guide/mm/
D	transhuge.rst	69 a flood of mmap system calls for every malloc(4k). Optimizing userland 238 Attempt to allocate huge pages every time we need a new page; 300 is incremented every time a huge page is successfully 319 is incremented every time a file huge page is successfully 323 is incremented every time a file huge page is mapped into 327 is incremented every time a huge page is split into base 343 is incremented every time a PMD split into table of PTEs. 349 is incremented every time a huge zero page is 352 every map of the huge zero page, only its allocation. 359 is incremented every time a huge page is swapout in one [all …]
/kernel/linux/linux-4.19/tools/perf/Documentation/
D	perf-script-python.txt	74 every time a system call occurs in the system. Our script will do 79 - we could enable every event under the tracing/events/syscalls 102 The options basically say to collect data for every syscall event 161 path append which every perf script script should include. 169 every event in the 'perf record' output. The handler functions take 176 generated for every script. The first, trace_unhandled(), is called 177 every time the script finds an event in the perf.data file that 206 Of course, for this script, we're not interested in printing every 234 store that information; every time the sys_enter() handler is called, 421 the event types in the trace file; it simply prints every available [all …]
D	perf-script-perl.txt	27 the event types in the trace file; it simply prints every available 91 to every event as arguments but are available as library functions. 107 The above provides the basics needed to directly access every field of 108 every event in a trace, which covers 90% of what you need to know to 114 Every perf script Perl script should start by setting up a Perl module 129 Aside from the event handler functions discussed above, every script 196 $context variable passed into every event handler as the second
/kernel/linux/linux-5.10/tools/perf/Documentation/
D	perf-script-python.txt	74 every time a system call occurs in the system. Our script will do 79 - we could enable every event under the tracing/events/syscalls 102 The options basically say to collect data for every syscall event 161 path append which every perf script script should include. 169 every event in the 'perf record' output. The handler functions take 176 generated for every script. The first, trace_unhandled(), is called 177 every time the script finds an event in the perf.data file that 206 Of course, for this script, we're not interested in printing every 234 store that information; every time the sys_enter() handler is called, 421 the event types in the trace file; it simply prints every available [all …]
D	perf-script-perl.txt	27 the event types in the trace file; it simply prints every available 91 to every event as arguments but are available as library functions. 107 The above provides the basics needed to directly access every field of 108 every event in a trace, which covers 90% of what you need to know to 114 Every perf script Perl script should start by setting up a Perl module 129 Aside from the event handler functions discussed above, every script 196 $context variable passed into every event handler as the second
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
D	transhuge.rst	69 a flood of mmap system calls for every malloc(4k). Optimizing userland 245 Attempt to allocate huge pages every time we need a new page; 307 is incremented every time a huge page is successfully 330 is incremented every time a file huge page is successfully 343 is incremented every time a file huge page is mapped into 347 is incremented every time a huge page is split into base 363 is incremented every time a PMD split into table of PTEs. 369 is incremented every time a huge zero page is 372 every map of the huge zero page, only its allocation. 379 is incremented every time a huge page is swapout in one [all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/gt/
D	intel_breadcrumbs_types.h	`15 * Rather than have every client wait upon all user interrupts, 16 * with the herd waking after every interrupt and each doing the 19 * every interrupt, we wake up one client, who does the heavyweight`
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
D	ext-ctrls-image-source.rst	`24 Vertical blanking. The idle period after every frame during which no 26 Every line has length of the image width plus horizontal blanking at 31 Horizontal blanking. The idle period after every line of image data`
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/skylakex/
D	uncore-other.json	452 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 464 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 476 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 488 …"PublicDescription": "Counts every read request for 4 bytes of data made by a unit on the main die… 500 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 512 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 524 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 536 …"PublicDescription": "Counts every write request of 4 bytes of data made to the MMIO space of a ca… 548 …"PublicDescription": "Counts every read request for up to a 64 byte transaction of data made by a … 560 …"PublicDescription": "Counts every read request for up to a 64 byte transaction of data made by a … [all …]
/kernel/linux/linux-4.19/Documentation/locking/
D	lockdep-design.txt	`223 correctness) in the sense that for every simple, standalone single-task 241 once, to prove locking correctness - instead of having to trigger every 243 every possible hardirq and softirq nesting scenario (which is impossible 251 value is unique for every lock-chain in the system. Also, lock 258 that for every lock taken and for every irqs-enable event, it would 261 tens of thousands of checks for every event. 266 calculated, which hash is unique for every lock chain. The hash value,`
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/
D	virtual-memory.json	`23 …"PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk … 42 …"PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fet… 61 …"PublicDescription": "This event counts every cycle when a data (D) page walk or instruction (I) p…`
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmont/
D	virtual-memory.json	`4 …"PublicDescription": "Counts every core cycle when a Data-side (walks due to a data operation) pag… 14 …"PublicDescription": "Counts every core cycle when a Instruction-side (walks due to an instruction… 24 …"PublicDescription": "Counts every core cycle a page-walk is in progress due to either a data memo…`
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/goldmont/
D	virtual-memory.json	`4 …"PublicDescription": "Counts every core cycle when a Data-side (walks due to a data operation) pag… 14 …"PublicDescription": "Counts every core cycle when a Instruction-side (walks due to an instruction… 24 …"PublicDescription": "Counts every core cycle a page-walk is in progress due to either a data memo…`

12 3 4 5 6 7 8 9 10 >>...166