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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:either (Results 1 – 25 of 8862) sorted by relevance

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

/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power8/
D	cache.json	6 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 12 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 18 …ded from another chip's L4 on a different Node or Group (Distant) due to either only demand loads … 24 …n": "The processor's data cache was reloaded from local core's L2 due to either only demand loads … 36 …cache was reloaded from a location other than the local core's L2 due to either only demand loads … 42 …he was reloaded from local core's L2 with load hit store conflict due to either only demand loads … 48 …ta cache was reloaded from local core's L2 with dispatch conflict due to either only demand loads … 54 …from local core's L2 hit without dispatch conflicts on Mepf state due to either only demand loads … 60 …r's data cache was reloaded from local core's L2 without conflict due to either only demand loads … 66 …n": "The processor's data cache was reloaded from local core's L3 due to either only demand loads … [all …]
D	frontend.json	90 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fet… 96 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fet… 102 …ded from another chip's L4 on a different Node or Group (Distant) due to either an instruction fet… 108 …ed from another chip's memory on the same Node or Group (Distant) due to either an instruction fet… 114 …e processor's Instruction cache was reloaded from local core's L2 due to either an instruction fet… 120 …cache was reloaded from a location other than the local core's L2 due to either an instruction fet… 126 …he was reloaded from local core's L2 with load hit store conflict due to either an instruction fet… 132 …on cache was reloaded from local core's L2 with dispatch conflict due to either an instruction fet… 138 …rom local core's L2 hit without dispatch conflicts on Mepf state. due to either an instruction fet… 144 …truction cache was reloaded from local core's L2 without conflict due to either an instruction fet… [all …]
D	other.json	35 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 65 …"BriefDescription": "Final Pump Scope (system) mispredicted. Either the original scope was too sma… 365 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for either de… 371 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either demand loads or da… 372 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 377 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either demand loads or da… 378 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 383 …ded from another chip's L4 on a different Node or Group (Distant) due to either demand loads or da… 384 …ded from another chip's L4 on a different Node or Group (Distant) due to either only demand loads … 389 …ed from another chip's memory on the same Node or Group (Distant) due to either demand loads or da… [all …]
D	memory.json	18 …ed from another chip's memory on the same Node or Group (Distant) due to either only demand loads … 24 … processor's data cache was reloaded from the local chip's Memory due to either only demand loads … 30 … from a memory location including L4 from local remote or distant due to either only demand loads … 36 …loaded from another chip's L4 on the same Node or Group ( Remote) due to either only demand loads … 42 …ed from another chip's memory on the same Node or Group ( Remote) due to either only demand loads … 53 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 83 …"BriefDescription": "Final Pump Scope (system) mispredicted. Either the original scope was too sma… 119 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 203 …"BriefDescription": "Final Pump Scope (system) mispredicted. Either the original scope was too sma…
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power8/
D	cache.json	6 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 12 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 18 …ded from another chip's L4 on a different Node or Group (Distant) due to either only demand loads … 24 …n": "The processor's data cache was reloaded from local core's L2 due to either only demand loads … 36 …cache was reloaded from a location other than the local core's L2 due to either only demand loads … 42 …he was reloaded from local core's L2 with load hit store conflict due to either only demand loads … 48 …ta cache was reloaded from local core's L2 with dispatch conflict due to either only demand loads … 54 …from local core's L2 hit without dispatch conflicts on Mepf state due to either only demand loads … 60 …r's data cache was reloaded from local core's L2 without conflict due to either only demand loads … 66 …n": "The processor's data cache was reloaded from local core's L3 due to either only demand loads … [all …]
D	frontend.json	90 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fet… 96 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fet… 102 …ded from another chip's L4 on a different Node or Group (Distant) due to either an instruction fet… 108 …ed from another chip's memory on the same Node or Group (Distant) due to either an instruction fet… 114 …e processor's Instruction cache was reloaded from local core's L2 due to either an instruction fet… 120 …cache was reloaded from a location other than the local core's L2 due to either an instruction fet… 126 …he was reloaded from local core's L2 with load hit store conflict due to either an instruction fet… 132 …on cache was reloaded from local core's L2 with dispatch conflict due to either an instruction fet… 138 …rom local core's L2 hit without dispatch conflicts on Mepf state. due to either an instruction fet… 144 …truction cache was reloaded from local core's L2 without conflict due to either an instruction fet… [all …]
D	other.json	35 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 65 …"BriefDescription": "Final Pump Scope (system) mispredicted. Either the original scope was too sma… 365 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for either de… 371 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either demand loads or da… 372 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 377 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either demand loads or da… 378 …p's L2 or L3 on a different Node or Group (Distant), as this chip due to either only demand loads … 383 …ded from another chip's L4 on a different Node or Group (Distant) due to either demand loads or da… 384 …ded from another chip's L4 on a different Node or Group (Distant) due to either only demand loads … 389 …ed from another chip's memory on the same Node or Group (Distant) due to either demand loads or da… [all …]
D	memory.json	18 …ed from another chip's memory on the same Node or Group (Distant) due to either only demand loads … 24 … processor's data cache was reloaded from the local chip's Memory due to either only demand loads … 30 … from a memory location including L4 from local remote or distant due to either only demand loads … 36 …loaded from another chip's L4 on the same Node or Group ( Remote) due to either only demand loads … 42 …ed from another chip's memory on the same Node or Group ( Remote) due to either only demand loads … 53 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 83 …"BriefDescription": "Final Pump Scope (system) mispredicted. Either the original scope was too sma… 119 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 203 …"BriefDescription": "Final Pump Scope (system) mispredicted. Either the original scope was too sma…
/kernel/linux/linux-6.6/drivers/firmware/xilinx/
D	zynqmp.c	130 * Return: Returns status, either success or error+reason 160 * Return: Returns status, either success or error+reason 236 * Return: Returns status, either success or error+reason 256 * Return: Returns status, either success or error+reason 317 * Return: Returns status, either success or error+reason 364 * Return: Returns status, either success or error+reason 415 * Return: Returns status, either success or error+reason 447 * Return: Returns status, either success or error+reason 504 * Return: Returns status, either success or error+reason 529 * Return: Returns status, either success or error+reason [all …]
/kernel/linux/linux-5.10/drivers/firmware/xilinx/
D	zynqmp.c	101 * Return: Returns status, either success or error+reason 131 * Return: Returns status, either success or error+reason 154 * Return: Returns status, either success or error+reason 217 * Return: Returns status, either success or error+reason 248 * Return: Returns status, either success or error+reason 298 * Return: Returns status, either success or error+reason 355 * Return: Returns status, either success or error+reason 380 * Return: Returns status, either success or error+reason 395 * Return: Returns status, either success or error+reason 411 * Return: Returns status, either success or error+reason [all …]
/kernel/linux/linux-5.10/lib/crypto/
D	Kconfig	`16 either builtin or as a module. 32 either builtin or as a module. 50 by either the generic implementation or an arch-specific one, if one 58 either builtin or as a module. 76 fulfilled by either the generic implementation or an arch-specific 94 either builtin or as a module. 111 by either the generic implementation or an arch-specific one, if one`
/kernel/linux/linux-6.6/lib/crypto/
D	Kconfig	`28 either builtin or as a module. 44 either builtin or as a module. 62 by either the generic implementation or an arch-specific one, if one 70 either builtin or as a module. 88 fulfilled by either the generic implementation or an arch-specific 106 either builtin or as a module. 123 by either the generic implementation or an arch-specific one, if one`
/kernel/linux/linux-6.6/Documentation/ABI/testing/
D	sysfs-platform-msi-laptop	`13 Enable automatic brightness control: contains either 0 or 1. If 22 WLAN subsystem enabled: contains either 0 or 1. 29 Bluetooth subsystem enabled: contains either 0 or 1. Please 38 Contains either 0 or 1 and indicates if touchpad is turned on. 46 Contains either 0 or 1 and indicates if turbo mode is turned 59 Contains either 0 or 1 and indicates if ECO mode is turned on. 80 Contains either 0 or 1 and indicates if fan speed is controlled`
/kernel/linux/linux-5.10/Documentation/ABI/testing/
D	sysfs-platform-msi-laptop	`13 Enable automatic brightness control: contains either 0 or 1. If 22 WLAN subsystem enabled: contains either 0 or 1. 29 Bluetooth subsystem enabled: contains either 0 or 1. Please 38 Contains either 0 or 1 and indicates if touchpad is turned on. 46 Contains either 0 or 1 and indicates if turbo mode is turned 59 Contains either 0 or 1 and indicates if ECO mode is turned on. 80 Contains either 0 or 1 and indicates if fan speed is controlled`
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/verifier/
D	var_off.c	8 /* add it to skb. We now have either &skb->len or 30 /* add it to fp. We now have either fp-4 or fp-8, but 52 /* add it to fp. We now have either fp-4 or fp-8, but 73 /* Add it to fp. We now have either fp-8 or fp-16, but 109 /* Add it to fp. We now have either fp-8 or fp-16, but 175 /* add it to fp. We now have either fp-4 or fp-8, but 200 /* add it to fp. We now have either fp-516 or fp-512, but 225 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know 250 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know 276 /* Add it to fp. We now have either fp-12 or fp-16, we don't know [all …]
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/
D	verifier_var_off.c	25 /* add it to skb. We now have either &skb->len or\ in variable_offset_ctx_access() 51 /* add it to fp. We now have either fp-4 or fp-8, but\ in stack_read_priv_vs_unpriv() 74 /* add it to fp. We now have either fp-4 or fp-8, but\ in variable_offset_stack_read_uninitialized() 105 /* Add it to fp. We now have either fp-8 or \ in stack_write_priv_vs_unpriv() 143 /* Add it to fp. We now have either fp-8 or fp-16, but\ in stack_write_followed_by_read() 185 /* Add it to fp. We now have either fp-8 or fp-16, but\ in stack_write_clobbers_spilled_regs() 251 /* add it to fp. We now have either fp-4 or fp-8, but\ in access_max_out_of_bound() 280 /* add it to fp. We now have either fp-516 or fp-512, but\ in access_min_out_of_bound() 310 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know\ in access_min_off_min_initialized() 343 /* Add it to fp. We now have either fp-12 or fp-16, we don't know\ in stack_access_priv_vs_unpriv() [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/
D	uncore-io.json	15 … on either NCB or NCS are in use. Transactions from the BL ring going into the IIO Agent must fir… 24 … on either NCB or NCS are in use. Transactions from the BL ring going into the IIO Agent must fir… 33 … on either NCB or NCS are in use. Transactions from the BL ring going into the IIO Agent must fir… 42 …r of times that a request pending in the BL Ingress attempted to acquire either a NCB or NCS credi… 51 …r of times that a request pending in the BL Ingress attempted to acquire either a NCB or NCS credi… 60 …r of times that a request pending in the BL Ingress attempted to acquire either a NCB or NCS credi… 69 … on either NCB or NCS are in use. Transactions from the BL ring going into the IIO Agent must fir… 78 … on either NCB or NCS are in use. Transactions from the BL ring going into the IIO Agent must fir… 87 … on either NCB or NCS are in use. Transactions from the BL ring going into the IIO Agent must fir…
/kernel/linux/linux-5.10/drivers/pci/controller/dwc/
D	Kconfig	33 This controller can work either as EP or RC. In order to enable 48 This controller can work either as EP or RC. In order to enable 65 This controller can work either as EP or RC. In order to enable 80 This controller can work either as EP or RC. In order to enable 141 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX] 153 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX] 263 Tegra194. This controller can work either as EP or RC. In order to 278 Tegra194. This controller can work either as EP or RC. In order to
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power10/
D	others.json	`15 "BriefDescription": "Cycles in which Superslice 0 dispatches either 1 or 2 instructions." 45 "BriefDescription": "Cycles in which Superslice 1 dispatches either 1 or 2 instructions." 50 "BriefDescription": "Cycles in which Superslice 1 dispatches either 3 or 4 instructions." 75 "BriefDescription": "Cycles in which Superslice 0 dispatches either 3 or 4 instructions." 80 "BriefDescription": "Cycles in which Superslice 0 dispatches either 5, 6, 7 or 8 instructions."`
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sandybridge/
D	cache.json	586 …code reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 631 …ch data reads that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 640 …data reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 676 …ch code reads that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 685 …code reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 721 …ch data reads that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 730 …data reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 766 …prefetch RFOs that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 775 …fetch RFOs that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 820 …d & prefetch) that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … [all …]
/kernel/linux/linux-6.6/arch/mips/include/asm/octeon/
D	cvmx-spi.h	`90 * active) or as a halfplex (either the Tx data path is 108 * active) or as a halfplex (either the Tx data path is 177 * active) or as a halfplex (either the Tx data path is 193 * active) or as a halfplex (either the Tx data path is 210 * active) or as a halfplex (either the Tx data path is 227 * active) or as a halfplex (either the Tx data path is 244 * active) or as a halfplex (either the Tx data path is 261 * active) or as a halfplex (either the Tx data path is`
/kernel/linux/linux-5.10/arch/mips/include/asm/octeon/
D	cvmx-spi.h	`90 * active) or as a halfplex (either the Tx data path is 108 * active) or as a halfplex (either the Tx data path is 177 * active) or as a halfplex (either the Tx data path is 193 * active) or as a halfplex (either the Tx data path is 210 * active) or as a halfplex (either the Tx data path is 227 * active) or as a halfplex (either the Tx data path is 244 * active) or as a halfplex (either the Tx data path is 261 * active) or as a halfplex (either the Tx data path is`
/kernel/linux/linux-6.6/drivers/pci/controller/dwc/
D	Kconfig	109 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX] 121 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX] 216 Tegra194. This controller can work either as EP or RC. In order to 231 Tegra194. This controller can work either as EP or RC. In order to 248 This controller can work either as EP or RC. In order to enable 263 This controller can work either as EP or RC. In order to enable 362 This controller can work either as EP or RC. In order to enable 377 This controller can work either as EP or RC. In order to enable
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/frequency/
D	adi,adrf6780.yaml	`55 Intermediate Frequency Mode Enable. Either IF Mode or I/Q Mode 61 I/Q Mode Enable. Either IF Mode or I/Q Mode can be enabled at a 68 Oscillator Input Frequency. Either LOx1 or LOx2 can be enabled 75 output frequency (LO x1). Either LOx1 or LOx2 can be enabled`
/kernel/linux/linux-5.10/arch/mips/kernel/
D	jump_label.c	`23 * - the ISA bit of the target, either 0 or 1 respectively, 26 * immediate field of the machine instruction, either 2 or 1, 29 * delay-slot instruction, either 256MB or 128MB, 31 * - the jump target alignment, either 4 or 2 bytes.`

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