Searched full:reliably (Results 1 – 25 of 48) sorted by relevance
12
144 state is in an inconsistent state, it may not be possible to reliably unwind,173 unwinder can reliably determine the original return address and no unwind state217 location of the return address cannot be reliably determined.249 Architectures must either ensure that unwinders either reliably unwind305 Due to cases such as the above, it may only be possible to reliably consume a308 reliably identify when the LR or stack value should be used (e.g. using
31 specific applications to reliably identify the driver.
140 means applications cannot *reliably* scan for loaded or installed
47 May be omitted if EDID works reliably.
72 to work reliably.
22 the messages can always be reliably determined.
103 such that the cache can reliably recover from unclean shutdown;
70 Reason for this is that the RTC is the only reliably available piece of
49 but interrupt behaviour is not guaranteed to work reliably. In test mode, the
108 reliably.
84 userspace is able to reliably determine which PMC the event is scheduled on.
47 - Stacks in vmalloc space need to work reliably. For example, if
186 certain scenarios. The way to disable callbacks reliably is to reset the
106 * Provide a detect function if and only if a chip can be detected reliably.
93 be reliably detected in ndo_fix_features. In this case, the callback
209 be reliably poll()'d or read() from while in this mode.
171 reliably if only connected two machines are connected using FireWire.
50 reliably unwind across interrupts and exceptions. Frame pointer based
36 Features cannot be probed reliably through other means. When a feature
181 Some parallel ports cannot reliably transfer data at full speed. To
304 We need this to be able to get a prompt reliably.
36 Users that want to reliably query this information more than once have
138 "culprit commit") is reliably identified. Some regressions can be fixed without161 time-consuming to reliably reproduce the issue, consider teaming up with other
42 estimate reliably the duration of audio buffers when handling
222 such as locks that were taken to be reliably released. There is *no*