Lines Matching refs:will
90 Therefore interrupts, including timer interrupts, will not arrive
104 If busy wait loops do exist, they will behave as infinite loops and
105 will stall the execution. For example, the following busy wait loop code,
106 which could be interrupted on actual hardware, will stall the execution of
114 updated by an interrupt handler or another thread, will also stall
123 - Code that depends on its own execution speed will normally not
124 work as expected. For example, code such as shown below, will likely not
147 If a busy wait loop exists, it will become evident as the application will be
149 pause it after the execution is stuck; it will be paused in
180 :kconfig:option:`CONFIG_USERSPACE` will always be disabled,
181 and all calls into the kernel will be done as normal calls.
250 addresses your binary will simply segfault.
251 The drivers and HW models for this architecture will hide this from the
340 Then the `native simulator <https://github.com/BabbleSim/native_simulator/>`_ runner will be built.
341 And after both the "embedded SW" and the runner will be linked together to form the final Linux
365 can be resolved inside that library will be resolved. And that, after, all these library symbols,
366 except a selected few marked with an special annotation, will be hidden from further linking.
367 In this way, the runner link stage will not link to or conflict with any of these hidden symbols,
383 will be linkable in the final link stage unless another embedded symbol with the same name was
386 ``NATIVE_SIMULATOR_IF`` macro will be linkable.
479 These allow registering (at build/link time) embedded context functions which will be called