Searched full:knows (Results 1 – 25 of 502) sorted by relevance
12345678910>>...21
| /Linux-v5.4/Documentation/RCU/ |
| D | rcu_dereference.txt | 24 the section entitled "EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH"
29 The compiler simply knows too much about integral values to
94 Because the compiler now knows that the value of "p" is exactly
109 compiler knows that the pointer is NULL, you had better
173 However, please note that if the compiler knows that the
301 EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH
310 But without rcu_dereference(), the compiler knows more than you might
343 Because the compiler can see all stores to "gp", it knows that the only
|
| /Linux-v5.4/tools/power/cpupower/man/ |
| D | cpupower-idle-info.1 | 49 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
|
| /Linux-v5.4/arch/powerpc/sysdev/xics/ |
| D | ics-opal.c | 187 /* 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()
|
| /Linux-v5.4/arch/x86/xen/ |
| D | xen-asm_64.S | 132 * Neither Xen nor the kernel really knows what the old SS and
150 * Neither Xen nor the kernel really knows what the old SS and
|
| /Linux-v5.4/include/crypto/ |
| D | akcipher.h | 71 * function, which knows how to decode and interpret
74 * function, which knows how to decode and interpret
376 * Function invokes the algorithm specific set key function, which knows
398 * Function invokes the algorithm specific set key function, which knows
|
| /Linux-v5.4/drivers/gpu/drm/ast/ |
| D | Kconfig | 10 and a version of AST that knows to fail if KMS
|
| /Linux-v5.4/drivers/phy/qualcomm/ |
| D | phy-qcom-ufs-qmp-20nm.c | 78 * Before any transactions involving PHY, ensure PHY knows in ufs_qcom_phy_qmp_20nm_power_control()
114 * ensure that PHY knows its PHY analog rail is going in ufs_qcom_phy_qmp_20nm_power_control()
|
| /Linux-v5.4/Documentation/ |
| D | mailbox.txt | 33 or it can never know (the client knows by way of the protocol).
86 /* The controller already knows async_pkt and sync_pkt */
|
| /Linux-v5.4/drivers/md/persistent-data/ |
| D | dm-transaction-manager.h | 74 * 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
|
| /Linux-v5.4/Documentation/process/ |
| D | volatile-considered-harmful.rst | 40 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
|
| /Linux-v5.4/fs/dlm/ |
| D | Kconfig | 17 list of resource and locks the local node knows about.
|
| /Linux-v5.4/include/linux/ |
| D | highmem.h | 197 …oed_user_highpage_movable - Allocate a zeroed HIGHMEM page for a VMA that the caller knows can move
201 * This function will allocate a page for a VMA that the caller knows will
|
| /Linux-v5.4/Documentation/i2c/ |
| D | functionality.rst | 25 I2C_FUNC_PROTOCOL_MANGLING Knows about the I2C_M_IGNORE_NAK,
119 successful, then the driver knows that it can call the following
|
| D | ten-bit-addresses.rst | 5 The I2C protocol knows about two kinds of device addresses: normal 7 bit
|
| /Linux-v5.4/arch/powerpc/kernel/ |
| D | note.S | 14 * Bit 0 indicates that the powerpc kernel binary knows how to run in an
|
| /Linux-v5.4/arch/sparc/prom/ |
| D | bootstr_64.c | 13 /* WARNING: The boot loader knows that these next three variables come one right
|
| /Linux-v5.4/Documentation/PCI/ |
| D | msi-howto.rst | 56 knows that all the data has arrived in memory.
225 lucky, the manufacturer knows this and has indicated it in the ACPI
245 Linux mostly knows about them and automatically enables MSIs if it can.
|
| /Linux-v5.4/Documentation/ia64/ |
| D | serial.rst | 54 EFI knows what your console devices are, but it doesn't tell the
82 The kernel can't start using a serial console until it knows where
|
| /Linux-v5.4/Documentation/scsi/ |
| D | scsi-changer.txt | 28 changers. But it allows to handle nearly all possible cases. It knows
53 software (anybody knows ???) which supports a BSDish changer driver,
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | elfnote.rst | 24 Indicate that the powerpc kernel binary knows how to run in an
|
| /Linux-v5.4/drivers/pci/ |
| D | setup-irq.c | 59 /* Always tell the device, so the driver knows what is in pci_assign_irq()
|
| /Linux-v5.4/Documentation/crypto/ |
| D | crypto_engine.rst | 25 using container_of. In addition, the engine knows nothing about your
|
| /Linux-v5.4/arch/microblaze/kernel/cpu/ |
| D | pvr.c | 19 * Until we get an assembler that knows about the pvr registers,
|
| /Linux-v5.4/include/linux/sched/ |
| D | clock.h | 8 * Do not use outside of architecture code which knows its limitations.
|
| /Linux-v5.4/arch/alpha/include/asm/ |
| D | string.h | 9 * EGCS 1.1 knows all about expanding memcpy inline, others don't.
|
12345678910>>...21
