- Used by Breath of the Wild.

Require by Zelda Breath Of The Wild

These mappings are leftovers from citra and don't apply to the Switch.

Given if we hit here all is lost, we should probably be logging the
break reason code and associated information to distinguish between the
causes.

- Used by Super Mario Odyssey.

Previously we weren't always initializing all members of the struct.
Prevents potentially wonky behavior from occurring.

Avoids potential One Definition Rule violations when these are used in
the future.

These currently aren't used and contain commented out source code that
corresponds to Dolphin's JIT. Given our CPU code is organized quite
differently, we shouldn't be keeping this around (at the moment it just
adds to compile times marginally).

The filter is returned via const reference, so this was making a
pointless copy of the entire filter every time a message was being
pushed into the logger instance.

Ensures both variants go through the same interface, and while we're at
it, add Finalize to provide the inverse of Initialize for consistency.

Now if changes are ever made to the behavior of the class, it doesn't
involve rebuilding everything that includes the mm_u header.

Orders elements in the precise order they'll be initialized.

- Used by Breath of the Wild.

linux-mingw does not really like this.

No longer required. HaltExecution is a no-op if it is not currently executing.

Needed for xenoblade

- Used by Breath of the Wild.

Despite being covered by a global mutex, we should still ensure that the
class handles its reference counts properly. This avoids potential
shenanigans when it comes to data races.

Given this is the root object that drives quite a bit of the kernel
object hierarchy, ensuring we always have the correct behavior (and no
races) is a good thing.

- Used by Breath of the Wild.

- Used by Breath of the Wild.

- Used by Breath of the Wild.

We divide the number of ticks to add by the number of cores (4) to obtain a more or less rough estimate of the actual number of ticks added. This assumes that all 4 cores are doing similar work. Previously we were adding ~4 times the number of ticks, thus making the games think that time was going way too fast.

This lets us bypass certain hangs in some games like Breath of the Wild.

We should modify our CoreTiming to support multiple cores (both running in a single thread, and in multiple host threads).

The current core may have nothing to do with the core where the new thread was scheduled to run. In case it's the same core, then the following PrepareReshedule call will take care of that.

Another thread may write to this variable while the core in question is in the middle of checking for a reschedule request.

Another thread might be in the middle of an SVC, thus altering the state of the schedulers.

Another thread might be in the middle of a reschedule, thus altering the state of the schedulers.

WakeAfterDelay might be called from any host thread, so err on the side of caution and use the thread-safe CoreTiming::ScheduleEventThreadsafe.

Note that CoreTiming is still far from thread-safe, there may be more things we have to work on for it to be up to par with what we want.

Exit from AddMutexWaiter early if the thread is already waiting for a mutex owned by the owner thread.

This accounts for the possibility of a thread that is waiting on a condition variable being awakened twice in a row.

Also added more validation asserts.

This should fix one of the random crashes in Breath Of The Wild.

Makes it consistent with the other VFS interfaces and prevents implicit
construction.