Lines Matching refs:will
17 must be provided. Interrupts are available. Kernel objects will most
22 Many drivers and subsystems will not work with this option
88 highest priority) that a thread will acquire as part of
97 threads at these priorities will always be scheduled before
106 that user code will not be executed (on the current CPU)
118 single priority will choose the next expiring deadline and
125 When true, the application will have access to the
145 threads have a single "assigned" CPU and they will never be
311 When selected, the scheduler ready queue will be implemented
314 Choose this on systems with constrained code size that will
323 When selected, the scheduler ready queue will be implemented
327 extra ~2kb of code. But the resulting behavior will scale
337 When selected, the scheduler ready queue will be implemented
364 When selected, the wait_q will be implemented with a
370 will be somewhat slower (though this is not generally a
376 When selected, the wait_q will be implemented with a
741 specify HEAP_MEM_POOL_ADD_SIZE_* options, these will be added together
742 and the sum will be compared to the HEAP_MEM_POOL_SIZE value.
744 has the default 0 value), then the actual heap size will be rounded up
748 requirements, ends up being zero, then no system heap will be
823 this is disabled. Obviously timeout-related APIs will not
831 kernel APIs will be a 64 bit quantity, allowing the use of
881 If stack canaries are supported by the compiler, it will emit
890 will occur at build time.
941 Stack canaries will leave in the thread local storage and
942 each thread will have its own canary. This makes harder
956 When enabled, will enforce that a writable page isn't executable
991 misc/speculation.h will insert fence instructions or other appropriate