Lines Matching refs:will
30 will be declared in some header under ``include/`` or in another
79 the kernel configuration) will instead point to a special verification for
102 Note that not all syscalls will be included in the final binaries.
108 will always have their syscalls present in final binaries.
117 user mode, or exclusively in supervisor mode. The system will look for
119 :c:macro:`__ZEPHYR_USER__`, typically these will be added to the compiler
132 there will be a CPU exception as soon as it tries to do something it isn't
167 will be invoked instead.
192 return value. Depending on context it will either directly call the
218 Additional arguments will need to be passed in an array in the source memory
229 Upon return from the system call the value written to that buffer will be
313 expression which must evaluate to true otherwise the check will fail.
333 If any check fails, the macros will return a nonzero value. The macro
334 :c:macro:`K_OOPS()` can be used to induce a kernel oops which will kill the
380 user threads will never have access to. The implementation functions get passed
592 which guarantees that these checks will be made and a return value
615 This will also be addressed by #23030.