Searched full:assumptions (Results 1 – 25 of 235) sorted by relevance
12345678910
79 * Defines assumptions which can be enabled. Each of these can be enabled80 * individually. For maximum safety, don't enable any assumptions!128 * assumptions about correctness.189 /** helper macros for checking assumptions */
90 * Assumptions:141 * Assumptions:193 * Assumptions:257 * Assumptions:
83 assumptions about the previous state of the kernel stack.92 avoids making assumptions about the previous state of the kernel106 assumptions about the previous state of the kernel stack.
352 * Assumptions:425 * Assumptions:522 * Assumptions:711 * Assumptions:872 * Assumptions:935 * Assumptions:1030 * Assumptions:1158 * Note: If the assumptions change regarding the non-paged, non-cached, in dfx_driver_init()1244 * Assumptions:1441 * Assumptions:[all …]
9 * The implicit assumptions are:
20 logic restrictions and assumptions.
21 * like "riscv_mtime", to signify that these non-ISA assumptions must hold.
128 monitoring chips on PC motherboards, and thus used to embed some assumptions130 assumptions was that most adapters and devices drivers support the SMBUS_QUICK135 and complex components such as DVB adapters, those assumptions became more
97 reason for this is that older kernels make assumptions about the values in100 would violate these assumptions and cause malfunction.
97 * assumptions:177 * assumptions:
74 * Fixme: 59 bits is a fictive number and makes assumptions about processors
10 * assumptions are made:
97 * Few simplistic rules and assumptions made here: in dp_link_bit_depth_to_bpp()
22 * In order to avoid any assumptions from bootloader regarding WDT
72 * Instead it makes no assumptions on the content and ordering of the
60 * Check assumptions on ps3_ipi_virqs[] indexing. If this in ps3_smp_probe()
92 * If neither flag is set (e.g. older Xen releases) the assumptions are:
30 * The only reason to have several buffers is to accommodate assumptions
31 * We make no fairness assumptions. They have a cost.
13 * The entry code does no assumptions regarding:
143 /* Did you forget to fix assumptions on max features? */ in __virtio_test_bit()160 /* Did you forget to fix assumptions on max features? */ in __virtio_set_bit()177 /* Did you forget to fix assumptions on max features? */ in __virtio_clear_bit()
5 This guide is an attempt to make explicit the locking assumptions
12 /* Assumptions:
23 is given to the user if the assumptions made in continuous-voltage mode do
32 * following 2 assumptions. This may needs to be revisited if embedded firmware