summaryrefslogtreecommitdiff
path: root/src/core (follow)
Commit message (Collapse)AuthorAgeFilesLines
* applets: Correct usage of SignalStateChanged eventGravatar Zach Hilman2018-12-093-6/+4
| | | | This was causing some games (most notably Pokemon Quest) to softlock due to an event being fired when not supposed to. This also removes a hack wherein we were firing the state changed event when the game retrieves it, which is incorrect.
* Merge pull request #1875 from DarkLordZach/oss-ngword2Gravatar bunnei2018-12-063-1/+41
|\ | | | | system_archive: Implement open source NgWord2
| * system_archive: Implement open source NgWord2Gravatar Zach Hilman2018-12-063-1/+41
| |
* | Merge pull request #1861 from lioncash/resetGravatar bunnei2018-12-066-11/+101
|\ \ | |/ |/| kernel/svc: Correct behavior of svcResetSignal()
| * kernel/svc: Correct behavior of svcResetSignal()Gravatar Lioncash2018-12-041-4/+11
| | | | | | | | | | | | | | | | While partially correct, this service call allows the retrieved event to be null, as it also uses the same handle to check if it was referring to a Process instance. The previous two changes put the necessary machinery in place to allow for this, so we can simply call those member functions here and be done with it.
| * kernel/process: Make Process a WaitObjectGravatar Lioncash2018-12-043-6/+68
| | | | | | | | | | | | | | Process instances can be waited upon for state changes. This is also utilized by svcResetSignal, which will be modified in an upcoming change. This simply puts all of the WaitObject related machinery in place.
| * kernel/readable_event: Add member function for enforcing a strict reset contractGravatar Lioncash2018-12-042-1/+22
| | | | | | | | | | | | svcResetSignal relies on the event instance to have already been signaled before attempting to reset it. If this isn't the case, then an error code has to be returned.
* | Merge pull request #1867 from lioncash/allocGravatar bunnei2018-12-052-4/+3
|\ \ | | | | | | system_archive: Use a regular function pointer instead of std::function for the file-scope system archive array
| * | ng_word: Deduplicate use of a constant valueGravatar Lioncash2018-12-051-1/+1
| | | | | | | | | | | | | | | We've already given the constant to the vector itself, so we don't need to re-hardcode it in the array.
| * | system_archive: Use a regular function pointer instead of std::function for ↵Gravatar Lioncash2018-12-051-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | file-scope system archive array This allows the array to be constexpr. std::function is also allowed to allocate memory, which makes its constructor non-trivial, we definitely don't want to have all of these execute at runtime, taking up time before the application can actually load.
* | | Merge pull request #1866 from lioncash/cacheGravatar bunnei2018-12-051-8/+2
|\ \ \ | | | | | | | | service/ldr: Deduplicate instruction cache clearing code in LoadNro()
| * | | service/ldr: Deduplicate instruction cache clearing code in LoadNro()Gravatar Lioncash2018-12-051-8/+2
| |/ / | | | | | | | | | We don't need to specify all of the ARM interfaces explicitly.
* / / Call shrink_to_fit after page-table vector resizing to cause crt to actually ↵Gravatar heapo2018-12-051-0/+8
|/ / | | | | | | lower vector capacity. For 36-bit titles saves 800MB of commit.
* | Merge pull request #1704 from DarkLordZach/oss-sysarchiveGravatar bunnei2018-12-048-1/+227
|\ \ | |/ |/| file_sys: Implement open source system archives
| * file_sys: Implement system archive synthesizer for NgWord (806)Gravatar Zach Hilman2018-11-225-6/+61
| |
| * fsp_srv: Add support for using open source archive if not found in NANDGravatar Zach Hilman2018-11-151-0/+10
| |
| * file_sys: Add framework for synthesizing open source archivesGravatar Zach Hilman2018-11-153-0/+109
| |
| * vfs_vector: Add VFS backend for std::arrayGravatar Zach Hilman2018-11-151-0/+52
| | | | | | | | Allows using constexpr/static const data with VFS.
* | Merge pull request #1838 from lioncash/dedupGravatar bunnei2018-12-041-27/+26
|\ \ | | | | | | file_sys/registered_cache: Eliminate variable shadowing
| * | file_sys/registered_cache: Eliminate variable shadowingGravatar Lioncash2018-12-011-27/+26
| | | | | | | | | | | | | | | Also inverts if statements where applicable to allow unindenting code a little bit.
* | | Merge pull request #1836 from lioncash/unusedGravatar bunnei2018-12-041-1/+0
|\ \ \ | | | | | | | | crypto/key_manager: Remove unused variable in GetTicketblob()
| * | | crypto/key_manager: Remove unused variable in GetTicketblob()Gravatar Lioncash2018-12-011-1/+0
| |/ /
* | | kernel/svc: Remove unused header inclusionGravatar Lioncash2018-12-041-1/+0
| | |
* | | kernel/svc: Implement svcSignalEvent()Gravatar Lioncash2018-12-041-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | This function simply does a handle table lookup for a writable event instance identified by the given handle value. If a writable event cannot be found for the given handle, then an invalid handle error is returned. If a writable event is found, then it simply signals the event, as one would expect.
* | | kernel/svc: Implement svcCreateEvent()Gravatar Lioncash2018-12-042-1/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | svcCreateEvent operates by creating both a readable and writable event and then attempts to add both to the current process' handle table. If adding either of the events to the handle table fails, then the relevant error from the handle table is returned. If adding the readable event after the writable event to the table fails, then the writable event is removed from the handle table and the relevant error from the handle table is returned. Note that since we do not currently test resource limits, we don't check the resource limit table yet.
* | | Merge pull request #1845 from lioncash/nroGravatar bunnei2018-12-045-19/+23
|\ \ \ | | | | | | | | loader/{nro, nso}: Remove dependency on the System class
| * | | loader/nso: Remove dependency on the System classGravatar Lioncash2018-12-023-8/+11
| | | | | | | | | | | | | | | | | | | | Similar to the NRO changes, we can also pass the process explicitly as a parameter from Load instead of indirecting through the System class.
| * | | loader/nro: Make the static LoadNro function internally linkedGravatar Lioncash2018-12-022-7/+5
| | | | | | | | | | | | | | | | | | | | This simply acts as a forwarding function for the Load() function, so this doesn't need to be directly exposed.
| * | | loader/nro: Remove dependency on the System classGravatar Lioncash2018-12-022-10/+13
| | | | | | | | | | | | | | | | | | | | | | | | Load() is already given the process instance as a parameter, so instead of coupling the class to the System class, we can just forward that parameter to LoadNro()
* | | | Merge pull request #1853 from lioncash/eventGravatar bunnei2018-12-045-10/+19
|\ \ \ \ | | | | | | | | | | kernel/object: Amend handle types to distinguish between readable and writable events
| * | | | kernel/object: Amend handle types to distinguish between readable and ↵Gravatar Lioncash2018-12-045-10/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | writable events Two kernel object should absolutely never have the same handle ID type. This can cause incorrect behavior when it comes to retrieving object types from the handle table. In this case it allows converting a WritableEvent into a ReadableEvent and vice-versa, which is undefined behavior, since the object types are not the same. This also corrects ClearEvent() to check both kernel types like the kernel itself does.
* | | | | kernel/handle_table: Amend reference to CTR-OS in Create()Gravatar Lioncash2018-12-041-2/+3
| | | | | | | | | | | | | | | | | | | | Another hold-over from Citra.
* | | | | kernel/svc: Implement the resource limit svcGetInfo optionGravatar Lioncash2018-12-044-9/+34
|/ / / / | | | | | | | | | | | | | | | | Allows a process to register the resource limit as part of its handle table.
* | | | [Kernel::CreateThread] Match format specifiers to LOG_TRACE's argumentsGravatar V.Kalyuzhny2018-12-041-1/+1
| | | |
* | | | Merge pull request #1840 from lioncash/infoGravatar bunnei2018-12-031-50/+100
|\ \ \ \ | | | | | | | | | | svc: Reorganize svcGetInfo, handle more error cases for existing implemented info categories
| * | | | svc: Use the current process' handle table for retrieving the process ↵Gravatar Lioncash2018-12-021-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | instance to act upon The kernel uses the handle table of the current process to retrieve the process that should be used to retrieve certain information. To someone not familiar with the kernel, this might raise the question of "Ok, sounds nice, but doesn't this make it impossible to retrieve information about the current process?". No, it doesn't, because HandleTable instances in the kernel have the notion of a "pseudo-handle", where certain values allow the kernel to lookup objects outside of a given handle table. Currently, there's only a pseudo-handle for the current process (0xFFFF8001) and a pseudo-handle for the current thread (0xFFFF8000), so to retrieve the current process, one would just pass 0xFFFF8001 into svcGetInfo. The lookup itself in the handle table would be something like: template <typename T> T* Lookup(Handle handle) { if (handle == PSEUDO_HANDLE_CURRENT_PROCESS) { return CurrentProcess(); } if (handle == PSUEDO_HANDLE_CURRENT_THREAD) { return CurrentThread(); } return static_cast<T*>(&objects[handle]); } which, as is shown, allows accessing the current process or current thread, even if those two objects aren't actually within the HandleTable instance.
| * | | | svc: Reorganize svcGetInfo, handle more error cases for existing implemented ↵Gravatar Lioncash2018-12-021-50/+99
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | info categories Our implementation of svcGetInfo was slightly incorrect in that we weren't doing proper error checking everywhere. Instead, reorganize it to be similar to how the kernel seems to do it.
* | | | Merge pull request #1835 from lioncash/cache-globalGravatar bunnei2018-12-036-31/+17
|\ \ \ \ | | | | | | | | | | filesystem: De-globalize registered_cache_union
| * | | | filesystem: De-globalize registered_cache_unionGravatar Lioncash2018-12-016-31/+17
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We can just return a new instance of this when it's requested. This only ever holds pointers to the existing registed caches, so it's not a large object. Plus, this also gets rid of the need to keep around a separate member function just to properly clear out the union. Gets rid of one of five globals in the filesystem code.
* | | | Merge pull request #1803 from DarkLordZach/k-able-eventGravatar bunnei2018-12-0333-236/+397
|\ \ \ \ | | | | | | | | | | kernel: Divide Event into ReadableEvent and WritableEvent
| * | | | hle_ipc: Refactor SleepClientThread to avoid ReadableEventGravatar Zach Hilman2018-11-299-14/+14
| | | | |
| * | | | kernel/event: Reference ReadableEvent from WritableEventGravatar Zach Hilman2018-11-2930-311/+169
| | | | |
| * | | | core: Port all current usages of Event to Readable/WritableEventGravatar Zach Hilman2018-11-2925-153/+274
| | | | |
| * | | | hle_ipc: Use event pair for SleepClientThreadGravatar Zach Hilman2018-11-292-19/+22
| | | | |
| * | | | kernel: Add named event tableGravatar Zach Hilman2018-11-292-0/+30
| | | | | | | | | | | | | | | | | | | | Used to store ReadableEvents of all events on the system.
| * | | | kernel: Divide Event into ReadableEvent and WritableEventGravatar Zach Hilman2018-11-296-61/+210
| | | | | | | | | | | | | | | | | | | | More hardware accurate. On the actual system, there is a differentiation between the signaler and signalee, they form a client/server relationship much like ServerPort and ClientPort.
| * | | | kernel/object: Add descriptions to ResetTypesGravatar Zach Hilman2018-11-291-3/+3
| | | | |
* | | | | Merge pull request #1833 from lioncash/cleanGravatar bunnei2018-12-035-5/+97
|\ \ \ \ \ | | | | | | | | | | | | service/fsp_srv: Implement CleanDirectoryRecursively
| * | | | | file_sys: Override missing mutating functions to be stubbed out for ↵Gravatar Lioncash2018-11-302-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ReadOnlyVfsDirectory by default Ensures that read only indeed means read only.
| * | | | | service/fsp_srv: Implement CleanDirectoryRecursivelyGravatar Lioncash2018-11-305-5/+72
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is the same behavior-wise as DeleteDirectoryRecursively, with the only difference being that it doesn't delete the top level directory in the hierarchy, so given: root_dir/ - some_dir/ - File.txt - OtherFile.txt The end result is just: root_dir/
HIC SVNT DRACONES