Searched full:knows (Results 1 – 25 of 590) sorted by relevance
12345678910>>...24
/linux-6.14.4/Documentation/RCU/ |
D | rcu_dereference.rst | 41 the section entitled "EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH" 52 The compiler simply knows too much about integral values to 117 Because the compiler now knows that the value of "p" is exactly 132 compiler knows that the pointer is NULL, you had better 202 However, please note that if the compiler knows that the 341 EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH 351 But without rcu_dereference(), the compiler knows more than you might 384 Because the compiler can see all stores to "gp", it knows that the only
|
/linux-6.14.4/drivers/gpu/drm/nouveau/include/nvrm/535.113.01/common/shared/msgq/inc/msgq/ |
D | msgq_priv.h | 53 * why the 'flags' field must be set to 1. 'rxHdrOff' is how the GSP knows 58 * this way, the GSP knows when a new command is in the queue (it polls 59 * writePtr) and it knows how much free space is in the status queue (it
|
/linux-6.14.4/include/crypto/ |
D | sig.h | 30 * function, which knows how to decode and interpret 33 * function, which knows how to decode and interpret 226 * Function invokes the algorithm specific set key function, which knows 247 * Function invokes the algorithm specific set key function, which knows
|
D | akcipher.h | 64 * function, which knows how to decode and interpret 67 * function, which knows how to decode and interpret 338 * Function invokes the algorithm specific set key function, which knows 360 * Function invokes the algorithm specific set key function, which knows
|
/linux-6.14.4/arch/powerpc/sysdev/xics/ |
D | ics-opal.c | 161 /* 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()
|
/linux-6.14.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-6.14.4/arch/x86/xen/ |
D | xen-asm.S | 277 * Neither Xen nor the kernel really knows what the old SS and 297 * Neither Xen nor the kernel really knows what the old SS and 319 * Neither Xen nor the kernel really knows what the old SS and
|
/linux-6.14.4/Documentation/networking/ |
D | netmem.rst | 46 must delegate the dma mapping to the page_pool, which knows when 50 which knows when dma-syncing is (or is not) appropriate.
|
/linux-6.14.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-6.14.4/Documentation/driver-api/ |
D | mailbox.rst | 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-6.14.4/drivers/gpu/drm/ast/ |
D | Kconfig | 13 and a version of AST that knows to fail if KMS
|
/linux-6.14.4/fs/dlm/ |
D | Kconfig | 17 list of resource and locks the local node knows about.
|
/linux-6.14.4/drivers/md/persistent-data/ |
D | dm-transaction-manager.h | 75 * 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
|
/linux-6.14.4/fs/ |
D | nsfs.c | 137 * userspace knows about will be copied. If userspace provides a new in copy_ns_info_to_user() 138 * struct, only the bits that the kernel knows aobut will be copied and in copy_ns_info_to_user() 139 * the size value will be set to the size the kernel knows about. in copy_ns_info_to_user()
|
/linux-6.14.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
|
/linux-6.14.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-6.14.4/drivers/pci/ |
D | iomap.c | 168 * CONFIG_GENERIC_IOMAP case, because that's the code that knows about 181 * implement your own pci_iounmap() that knows the rules for where
|
/linux-6.14.4/drivers/misc/lkdtm/ |
D | fortify.c | 54 * compiler knows at build time that target.a < 20 bytes. Use a in lkdtm_FORTIFY_STR_MEMBER() 119 * compiler knows at build time that target.a < 20 bytes. Use a in lkdtm_FORTIFY_MEM_MEMBER()
|
/linux-6.14.4/drivers/md/dm-vdo/indexer/ |
D | index-page-map.h | 15 * that it knows it will need.
|
/linux-6.14.4/arch/powerpc/kernel/ |
D | note.S | 14 * Bit 0 indicates that the powerpc kernel binary knows how to run in an
|
/linux-6.14.4/arch/sparc/prom/ |
D | bootstr_64.c | 13 /* WARNING: The boot loader knows that these next three variables come one right
|
/linux-6.14.4/drivers/platform/x86/intel/atomisp2/ |
D | Kconfig | 26 the driver knows about.
|
/linux-6.14.4/Documentation/scsi/ |
D | scsi-changer.rst | 30 changers. But it allows to handle nearly all possible cases. It knows 57 software (anybody knows ???) which supports a BSDish changer driver,
|
/linux-6.14.4/Documentation/arch/powerpc/ |
D | elfnote.rst | 24 Indicate that the powerpc kernel binary knows how to run in an
|
/linux-6.14.4/Documentation/arch/x86/x86_64/ |
D | machinecheck.rst | 15 mcelog knows how to decode them.
|
12345678910>>...24