Previously core itself was the library containing the code to gather
common information (build info, CPU info, and OS info), however all of
this isn't core-dependent and can be moved to the common code and use
the common interfaces. We can then just call those functions from the
core instead.

This will allow replacing our CPU detection with Xbyak's which has
better detection facilities than ours. It also keeps more
architecture-dependent code in common instead of core.

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.

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

- Used by Breath of the Wild.

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.

struct should be used when the data type is very simple or otherwise has
no invariants associated with it. Given these are used to form a
hierarchy, class should be used instead.

This function doesn't modify instance state, so the const qualifier can
be added to it.

These don't directly modify the contained data.

Don't emut copies, especially not for data, which is used once. They just end in a huge GPU overhead.

Please see https://github.com/citra-emu/citra/pull/3666 for more details.

As we're not handling any anything about the revision data for GetAudioDeviceServiceWithRevisionInfo, it's currently marked as stubbed. However for games this shouldn't affect the result. Proper revision info would be more for homebrew.

Prevents clang-format from butchering them.

This is required by ARMS.