either (full) in projects: Linux-v5.4 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/Linux-v5.4/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 …ache was reloaded from a localtion 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 …ache was reloaded from a localtion 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…
/Linux-v5.4/drivers/firmware/xilinx/
D	zynqmp.c	80 * Return: Returns status, either success or error+reason 110 * Return: Returns status, either success or error+reason 152 * Return: Returns status, either success or error+reason 177 * Return: Returns status, either success or error+reason 225 * Return: Returns status, either success or error+reason 282 * Return: Returns status, either success or error+reason 306 * Return: Returns status, either success or error+reason 320 * Return: Returns status, either success or error+reason 335 * Return: Returns status, either success or error+reason 357 * Return: Returns status, either success or error+reason [all …]
/Linux-v5.4/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`
D	sysfs-bus-iio-temperature-max31856	`7 Reading returns either '1' or '0'. 21 Reading returns either '1' or '0'.`
/Linux-v5.4/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 80 /* add it to fp. We now have either fp-4 or fp-8, but 105 /* add it to fp. We now have either fp-516 or fp-512, but 130 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know 155 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know 181 /* Add it to fp. We now have either fp-12 or fp-16, we don't know 182 * which, but either way it points to initialized stack. 210 /* Add it to fp. We now have either fp-12 or fp-16, we don't know 211 * which, but either way it points to initialized stack. [all …]
/Linux-v5.4/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`
/Linux-v5.4/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 142 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX] 154 This controller can work either as EP or RC. The RCW[HOST_AGT_PEX]`
/Linux-v5.4/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.`
/Linux-v5.4/Documentation/virt/kvm/
D	s390-diag.txt	`16 all supported DIAGNOSE calls need to be handled by either KVM or its 43 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3). 46 the function's return code, which is either a return code or a subcode 59 Handled by either userspace or KVM (ioeventfd case).`
/Linux-v5.4/include/net/
D	mac802154.h	`167 * either zero or negative errno. Called with pib_lock held. 172 * Returns either zero, or negative errno. Called with pib_lock held. 177 * Returns either zero, or negative errno. 181 * Returns either zero, or negative errno. 186 * Returns either zero, or negative errno. 190 * Returns either zero, or negative errno. 195 * Returns either zero, or negative errno. 199 * Returns either zero, or negative errno. 203 * Returns either zero, or negative errno.`
/Linux-v5.4/Documentation/scsi/
D	scsi_eh.txt	43 Once LLDD gets hold of a scmd, either the LLDD will complete the 108 will either be retried (if the number of retries is not exhausted) 128 the host either complete normally, fail and get added to eh_cmd_q, or 131 If all scmds either complete or fail, the number of in-flight scmds 227 either retry or error-finish (notify upper layer of failure) recovered 327 either offline or ready, scsi_eh_finish_cmd() is invoked for 358 If STU succeeds and the sdev is either offline or ready, 410 flushes eh_done_q by either retrying or notifying upper 419 all failed scmds and either ready for new commands or offline. Also, 451 - Either scsi_queue_insert() or scsi_finish_command() is called on
D	LICENSE.FlashPoint	`8 the terms of either: 11 Foundation; either version 2, or (at your option) any later version, 19 or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public`
/Linux-v5.4/Documentation/devicetree/bindings/serial/
D	amlogic,meson-uart.yaml	`15 of SoCs, and can be present either in the "Always-On" power domain or the 49 - description: the bus core clock, either the clk81 clock or the gate clock 50 - description: the source of the baudrate generator, can be either the xtal or the pclk`
/Linux-v5.4/Documentation/admin-guide/gpio/
D	sysfs.rst	`75 reads as either "in" or "out". This value may 87 reads as either 0 (low) or 1 (high). If the GPIO 97 poll(2) returns, either lseek(2) to the beginning of the sysfs 102 reads as either "none", "rising", "falling", or 110 reads as either 0 (false) or 1 (true). Write`
/Linux-v5.4/tools/lib/traceevent/
D	trace-seq.c	`106 * The tracer may use either sequence operations or its own 109 * buffer (@s). Then the output may be either used by 148 * The tracer may use either sequence operations or its own 151 * buffer (@s). Then the output may be either used by 183 * The tracer may use either the sequence operations or its own`
/Linux-v5.4/kernel/trace/
D	trace_seq.c	`19 * A write to the buffer will either succed or fail. That is, unlike 78 * The tracer may use either sequence operations or its own 81 * buffer (@s). Then the output may be either used by 138 * The tracer may use either sequence operations or its own 141 * buffer (@s). Then the output may be either used by 203 * The tracer may use either the sequence operations or its own 231 * The tracer may use either the sequence operations or its own`
/Linux-v5.4/Documentation/devicetree/bindings/pinctrl/
D	pinctrl-bindings.txt	`59 used in an SoC either without a pin controller, or where the 108 driver for the pin controller. This property can be set either 148 (either this or "pins" must be specified) 149 pins - the list of pins to select with this function (either 242 apply to (either this, "group" or "pinmux" has to be 246 individual pins (either this, "pins" or "pinmux" has 249 that properties in the node apply to (either this,`
/Linux-v5.4/tools/perf/pmu-events/arch/x86/sandybridge/
D	cache.json	760 …code reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 796 …ch data reads that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 820 …data reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 856 …ch code reads that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 880 …code reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 916 …ch data reads that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 940 …data reads that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 976 …prefetch RFOs that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … 1000 …fetch RFOs that hit in the LLC and sibling core snoops are not needed as either the core-valid bit… 1036 …d & prefetch) that hit in the LLC and the snoops to sibling cores hit in either E/S state and the … [all …]
/Linux-v5.4/tools/perf/pmu-events/arch/x86/silvermont/
D	cache.json	86 …s the number of retired memory operations with lock semantics. These are either implicit locked in… 226 … (demand & prefetch) that miss L2 and the snoops to sibling cores hit in either E/S state and the … 281 … (demand & prefetch) that miss L2 and the snoops to sibling cores hit in either E/S state and the … 336 … (demand & prefetch) that miss L2 and the snoops to sibling cores hit in either E/S state and the … 391 … "Counts any request that miss L2 and the snoops to sibling cores hit in either E/S state and the … 446 …prefetcher data read that miss L2 and the snoops to sibling cores hit in either E/S state and the … 512 …ed by L2 prefetchers that miss L2 and the snoops to sibling cores hit in either E/S state and the … 556 …ed by L2 prefetchers that miss L2 and the snoops to sibling cores hit in either E/S state and the … 600 …ed by L2 prefetchers that miss L2 and the snoops to sibling cores hit in either E/S state and the … 666 …nstruction cacheline that miss L2 and the snoops to sibling cores hit in either E/S state and the … [all …]
/Linux-v5.4/LICENSES/deprecated/
D	GPL-1.0	`69 on the Program" means either the Program or any work containing the 70 Program or a portion of it, either verbatim or with modifications. Each 90 in whole or in part contains the Program or any part thereof, either 167 either of that version or of any later version published by the Free 185 PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 221 the Free Software Foundation; either version 1, or (at your option)`
/Linux-v5.4/drivers/pinctrl/aspeed/
D	pinmux-aspeed.c	`38 * is enabled). Thus we must explicitly test for either condition as required. 75 * If an expression's state is described by more than one bit, either through 79 * either condition as required.`
/Linux-v5.4/Documentation/x86/
D	mds.rst	`81 clearing. Either the modified VERW instruction or via the L1D Flush 116 off Mitigation is disabled. Either the CPU is not affected or 162 When SMT is inactive, i.e. either the CPU does not support it or all 184 flushed either on exit to user space or on VMENTER so malicious code 192 legacy interface which is only used on older systems which are either`

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