Rather than let the service call itself work out which function is the proper one to call, we can make that a behavior of the arbiter itself, so we don't need to directly expose those implementation details. |
||
---|---|---|
.. | ||
arm | ||
crypto | ||
file_sys | ||
frontend | ||
gdbstub | ||
hle | ||
loader | ||
tracer | ||
CMakeLists.txt | ||
core_cpu.cpp | ||
core_cpu.h | ||
core_timing_util.cpp | ||
core_timing_util.h | ||
core_timing.cpp | ||
core_timing.h | ||
core.cpp | ||
core.h | ||
cpu_core_manager.cpp | ||
cpu_core_manager.h | ||
memory_hook.cpp | ||
memory_hook.h | ||
memory_setup.h | ||
memory.cpp | ||
memory.h | ||
perf_stats.cpp | ||
perf_stats.h | ||
settings.cpp | ||
settings.h | ||
telemetry_session.cpp | ||
telemetry_session.h |