MCPcopy Create free account
hub / github.com/Bareflank/hypervisor / fail_entry

Function fail_entry

kernel/integration/bf_vs_op_destroy_vs.cpp:184–217  ·  view source on GitHub ↗

Source from the content-addressed store, hash-verified

182 /// input is undefined.
183 ///
184 extern "C" void
185 fail_entry(bsl::safe_u64::value_type const errc, bsl::safe_u64::value_type const addr) noexcept
186 {
187 /// NOTE:
188 /// - Call into the fast fail handler. This entry point serves as a
189 /// trampoline between C and C++. Specifically, the microkernel
190 /// cannot call a member function directly, and can only call
191 /// a C style function.
192 ///
193
194 auto const ret{dispatch_fail( // --
195 g_mut_gs, // --
196 g_mut_tls, // --
197 g_mut_sys, // --
198 g_mut_intrinsic, // --
199 g_mut_vp_pool, // --
200 g_mut_vs_pool, // --
201 bsl::to_u64(errc), // --
202 bsl::to_u64(addr))};
203
204 if (bsl::unlikely(!ret)) {
205 bsl::print<bsl::V>() << bsl::here();
206 return bf_control_op_exit();
207 }
208
209 /// NOTE:
210 /// - This code should never be reached. The fast fail handler should
211 /// always call one of the "run" ABIs to return back to the
212 /// microkernel when a fast fail is finished. If this is called, it
213 /// is because the fast fail handler returned with an error.
214 ///
215
216 return bf_control_op_exit();
217 }
218
219 /// <!-- description -->
220 /// @brief Implements the VMExit entry function. This is registered

Callers

nothing calls this directly

Calls 2

dispatch_failFunction · 0.50
bf_control_op_exitFunction · 0.50

Tested by

no test coverage detected