- Apr 01, 2019
-
-
Lioncash authored
Since C++17, the introduction of deduction guides for locking facilities means that we no longer need to hardcode the mutex type into the locks themselves, making it easier to switch mutex types, should it ever be necessary in the future.
-
- Mar 31, 2019
- Mar 30, 2019
-
-
bunnei authored
video_core/{gl_rasterizer, gpu_thread}: Remove unused class variables where applicable
-
bunnei authored
kernel/scheduler: Minor tidying up
-
bunnei authored
service/fatal: Name FatalInfo structure members
-
Lioncash authored
Since C++17, we no longer need to explicitly specify the type of the mutex within the lock_guard. The type system can now deduce these with deduction guides.
-
Lioncash authored
-
Lioncash authored
Resolves a -Wextra-semi warning.
-
Lioncash authored
Based off RE, most of these structure members are register values, which makes, sense given this service is used to convey fatal errors. One member indicates the program entry point address, one is a set of bit flags used to determine which registers to print, and one member indicates the architecture type. The only member that still isn't determined is the final member within the data structure.
-
- Mar 29, 2019
-
-
Lioncash authored
Many of these functions are carried over from Dolphin (where they aren't used anymore). Given these have no use (and we really shouldn't be screwing around with OS-specific thread scheduler handling from the emulator, these can be removed. The function for setting the thread name is left, however, since it can have debugging utility usages.
-
Lioncash authored
Reports the (mostly) correct size through svcGetInfo now for queries to total used physical memory. This still doesn't correctly handle memory allocated via svcMapPhysicalMemory, however, we don't currently handle that case anyways.
-
Lioncash authored
This will be necessary to properly report the used memory size in svcGetInfo.
-
bunnei authored
Kernel: Fixes to Arbitration and SignalProcessWideKey Management
-
bunnei authored
Replace old Thread Queue for a new Multi Level Queue
-
- Mar 28, 2019
-
-
Lioncash authored
This will be necessary in order to properly report memory usage within svcGetInfo.
-
Lioncash authored
This will make operating with the process-related SVC commands much nicer in the future (the parameter representing the stack size in svcStartProcess is a 64-bit value).
-
Lioncash authored
The kernel always makes sure that the given stack size is aligned to page boundaries.
-
bunnei authored
kernel/vm_manager: Unify heap allocation/freeing functions
-
bunnei authored
video_core: Add missing override specifiers
-
bunnei authored
video_core/gpu: Amend typo in GPU member variable name
-
- Mar 27, 2019
-
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Lioncash authored
The pusher instance is only ever used in the constructor of the ThreadManager for creating the thread that the ThreadManager instance contains. Aside from that, the member is unused, so it can be removed.
-
Lioncash authored
This member variable is no longer being used, so it can be removed, removing a dependency on EmuWindow from the rasterizer's interface"
-
Lioncash authored
Specifies the members in the same order that initialization would take place in. This also silences -Wreorder warnings.
-
Lioncash authored
Ensures that the signatures will always match with the base class. Also silences a few compilation warnings.
-
Lioncash authored
smaphore -> semaphore
-
- Mar 26, 2019
-
-
bunnei authored
kernel/process: Remove unused AddressMapping struct
-
bunnei authored
core/core_timing: Make callback parameters consistent
-
bunnei authored
kernel/kernel: Remove unnecessary forward declaration
-
bunnei authored
core/cheat_engine: Make MemoryReadImpl and MemoryWriteImpl internally linked
-
- Mar 24, 2019
-
-
Lioncash authored
These don't need to be visible outside of the translation unit, so they can be enclosed within an anonymous namespace.
-
Lioncash authored
In some cases, our callbacks were using s64 as a parameter, and in other cases, they were using an int, which is inconsistent. To make all callbacks consistent, we can just use an s64 as the type for late cycles, given it gets rid of the need to cast internally. While we're at it, also resolve some signed/unsigned conversions that were occurring related to the callback registration.
-