Home
last modified time | relevance | path

Searched full:knows (Results 1 – 25 of 1092) sorted by relevance

12345678910>>...44

/kernel/linux/linux-5.10/Documentation/RCU/
Drcu_dereference.rst27 the section entitled "EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH"
32 The compiler simply knows too much about integral values to
97 Because the compiler now knows that the value of "p" is exactly
112 compiler knows that the pointer is NULL, you had better
176 However, please note that if the compiler knows that the
305 EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH
315 But without rcu_dereference(), the compiler knows more than you might
348 Because the compiler can see all stores to "gp", it knows that the only
/kernel/linux/linux-6.6/Documentation/RCU/
Drcu_dereference.rst28 the section entitled "EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH"
39 The compiler simply knows too much about integral values to
104 Because the compiler now knows that the value of "p" is exactly
119 compiler knows that the pointer is NULL, you had better
189 However, please note that if the compiler knows that the
328 EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH
338 But without rcu_dereference(), the compiler knows more than you might
371 Because the compiler can see all stores to "gp", it knows that the only
/kernel/linux/linux-6.6/arch/powerpc/sysdev/xics/
Dics-opal.c161 /* Check if HAL knows about this interrupt */ in ics_opal_check()
175 /* Check if HAL knows about this interrupt */ in ics_opal_mask_unknown()
189 /* Check if HAL knows about this interrupt */ in ics_opal_get_server()
/kernel/linux/linux-6.6/tools/power/cpupower/man/
Dcpupower-idle-info.149 time. This state is used if the kernel knows that work has to be processed
69 The intel_idle driver knows the sleep state capabilities of the processor and
/kernel/linux/linux-5.10/tools/power/cpupower/man/
Dcpupower-idle-info.149 time. This state is used if the kernel knows that work has to be processed
69 The intel_idle driver knows the sleep state capabilities of the processor and
/kernel/linux/linux-6.6/arch/x86/xen/
Dxen-asm.S244 * Neither Xen nor the kernel really knows what the old SS and
264 * Neither Xen nor the kernel really knows what the old SS and
286 * Neither Xen nor the kernel really knows what the old SS and
/kernel/linux/linux-5.10/arch/powerpc/sysdev/xics/
Dics-opal.c187 /* Check if HAL knows about this interrupt */ in ics_opal_map()
204 /* Check if HAL knows about this interrupt */ in ics_opal_mask_unknown()
218 /* Check if HAL knows about this interrupt */ in ics_opal_get_server()
/kernel/linux/linux-5.10/arch/x86/xen/
Dxen-asm.S285 * Neither Xen nor the kernel really knows what the old SS and
304 * Neither Xen nor the kernel really knows what the old SS and
325 * Neither Xen nor the kernel really knows what the old SS and
/kernel/linux/linux-5.10/include/crypto/
Dakcipher.h71 * function, which knows how to decode and interpret
74 * function, which knows how to decode and interpret
378 * Function invokes the algorithm specific set key function, which knows
400 * Function invokes the algorithm specific set key function, which knows
/kernel/linux/linux-6.6/include/crypto/
Dsig.h112 * Function invokes the algorithm specific set key function, which knows
128 * Function invokes the algorithm specific set key function, which knows
Dakcipher.h96 * function, which knows how to decode and interpret
99 * function, which knows how to decode and interpret
461 * Function invokes the algorithm specific set key function, which knows
483 * Function invokes the algorithm specific set key function, which knows
/kernel/linux/linux-6.6/drivers/gpu/drm/ast/
DKconfig12 and a version of AST that knows to fail if KMS
/kernel/linux/linux-5.10/drivers/gpu/drm/ast/
DKconfig12 and a version of AST that knows to fail if KMS
/kernel/linux/linux-5.10/Documentation/process/
Dvolatile-considered-harmful.rst40 compiler might think it knows what will be in shared_data, but the
42 forget anything it knows. There will be no optimization problems with
/kernel/linux/linux-6.6/Documentation/driver-api/
Dmailbox.rst33 or it can never know (the client knows by way of the protocol).
86 /* The controller already knows async_pkt and sync_pkt */
/kernel/linux/linux-6.6/Documentation/process/
Dvolatile-considered-harmful.rst40 compiler might think it knows what will be in shared_data, but the
42 forget anything it knows. There will be no optimization problems with
/kernel/linux/linux-5.10/drivers/md/persistent-data/
Ddm-transaction-manager.h74 * this operation. Because the tm knows the scope of the transaction it
125 * The superblock location is passed so the metadata space map knows it
/kernel/linux/linux-5.10/Documentation/driver-api/
Dmailbox.rst33 or it can never know (the client knows by way of the protocol).
86 /* The controller already knows async_pkt and sync_pkt */
/kernel/linux/linux-5.10/fs/dlm/
DKconfig18 list of resource and locks the local node knows about.
/kernel/linux/linux-6.6/fs/dlm/
DKconfig17 list of resource and locks the local node knows about.
/kernel/linux/linux-6.6/drivers/md/persistent-data/
Ddm-transaction-manager.h75 * this operation. Because the tm knows the scope of the transaction it
142 * The superblock location is passed so the metadata space map knows it
/kernel/linux/linux-6.6/Documentation/i2c/
Dfunctionality.rst25 I2C_FUNC_PROTOCOL_MANGLING Knows about the I2C_M_IGNORE_NAK,
119 successful, then the driver knows that it can call the following
/kernel/linux/linux-6.6/lib/
Dpci_iomap.c140 * CONFIG_GENERIC_IOMAP case, because that's the code that knows about
153 * implement your own pci_iounmap() that knows the rules for where
/kernel/linux/linux-5.10/Documentation/i2c/
Dfunctionality.rst25 I2C_FUNC_PROTOCOL_MANGLING Knows about the I2C_M_IGNORE_NAK,
119 successful, then the driver knows that it can call the following
/kernel/linux/linux-5.10/arch/powerpc/kernel/
Dnote.S14 * Bit 0 indicates that the powerpc kernel binary knows how to run in an

12345678910>>...44