summaryrefslogtreecommitdiff
path: root/src/core/hle/kernel/mutex.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* core: hle: Integrate new KConditionVariable and KAddressArbiter implementations.Gravatar bunnei2021-01-111-170/+0
|
* hle: kernel: thread: Replace ThreadStatus/ThreadSchedStatus with a single ↵Gravatar bunnei2021-01-111-1/+1
| | | | | | ThreadState. - This is how the real kernel works, and is more accurate and simpler.
* core: hle: kernel: Update KSynchronizationObject.Gravatar bunnei2021-01-111-2/+2
|
* hle: kernel: Migrate to KScopedSchedulerLock.Gravatar bunnei2020-12-061-3/+3
|
* hle: kernel: Rewrite scheduler implementation based on Mesopshere.Gravatar bunnei2020-12-061-3/+3
|
* Clang Format.Gravatar Fernando Sahmkow2020-06-271-6/+5
|
* Kernel: Corrections to TimeManager, Scheduler and Mutex.Gravatar Fernando Sahmkow2020-06-271-2/+1
|
* Mutex: Revert workaround due to poor exclusive memory.Gravatar Fernando Sahmkow2020-06-271-9/+2
|
* ARM/Memory: Correct Exclusive Monitor and Implement Exclusive Memory Writes.Gravatar Fernando Sahmkow2020-06-271-2/+3
|
* Mutex: Correct Result writting to clear exclusivity.Gravatar Fernando Sahmkow2020-06-271-3/+11
|
* SVC: Correct ArbitrateUnlockGravatar Fernando Sahmkow2020-06-271-32/+33
|
* SVC: Correct SignalEvent, ClearEvent, ResetSignal, WaitSynchronization, ↵Gravatar Fernando Sahmkow2020-06-271-26/+39
| | | | CancelSynchronization, ArbitrateLock
* kernel: Don't fail silentlyGravatar David Marcec2020-04-291-0/+5
|
* kernel: Remove unnecessary includesGravatar Lioncash2019-12-071-0/+1
| | | | | | Over the course of the changes to the kernel code, a few includes are no longer necessary, particularly with the change over to std::shared_ptr from Boost's intrusive_ptr.
* core/memory: Migrate over Write{8, 16, 32, 64, Block} to the Memory classGravatar Lioncash2019-11-261-2/+2
| | | | | | | | | The Write functions are used slightly less than the Read functions, which make these a bit nicer to move over. The only adjustments we really need to make here are to Dynarmic's exclusive monitor instance. We need to keep a reference to the currently active memory instance to perform exclusive read/write operations.
* core/memory: Migrate over Read{8, 16, 32, 64, Block} to the Memory classGravatar Lioncash2019-11-261-1/+1
| | | | | | | | | | | | | | With all of the trivial parts of the memory interface moved over, we can get right into moving over the bits that are used. Note that this does require the use of GetInstance from the global system instance to be used within hle_ipc.cpp and the gdbstub. This is fine for the time being, as they both already rely on the global system instance in other functions. These will be removed in a change directed at both of these respectively. For now, it's sufficient, as it still accomplishes the goal of de-globalizing the memory code.
* kernel: Replace usage of boost::intrusive_ptr with std::shared_ptr for ↵Gravatar bunnei2019-11-241-10/+12
| | | | | | | | kernel objects. (#3154) * kernel: Replace usage of boost::intrusive_ptr with std::shared_ptr for kernel objects. - See https://github.com/citra-emu/citra/pull/4710 for details.
* Kernel: Correct Results in Condition Variables and MutexesGravatar Fernando Sahmkow2019-10-151-0/+1
|
* Kernel: Style and CorrectionsGravatar Fernando Sahmkow2019-10-151-1/+1
|
* Add PrepareReschedule where required.Gravatar Fernando Sahmkow2019-10-151-0/+2
|
* core/hle/kernel/mutex: Remove usages of global system accessorsGravatar Lioncash2019-03-141-11/+15
| | | | | Removes the use of global system accessors, and instead uses the explicit interface provided.
* core/hle/kernel: Make Mutex a per-process class.Gravatar Lioncash2019-03-141-2/+7
| | | | | | | Makes it an instantiable class like it is in the actual kernel. This will also allow removing reliance on global accessors in a following change, now that we can encapsulate a reference to the system instance in the class.
* general: Remove unused boost inclusions where applicableGravatar Lioncash2018-10-301-2/+0
| | | | Cleans up unused includes and trims off some dependencies on externals.
* kernel/mutex: Amend behavior of TransferMutexOwnership()Gravatar Lioncash2018-10-061-1/+1
| | | | | | | | | This was the result of a typo accidentally introduced in e51d715700a35a8f14e5b804b6f7553c9a40888b. This restores the previous correct behavior. The behavior with the reference was incorrect and would cause some games to fail to boot.
* kernel/thread: Make all instance variables privateGravatar Lioncash2018-10-041-17/+17
| | | | | | | | | | | | | | | | | | | | Many of the member variables of the thread class aren't even used outside of the class itself, so there's no need to make those variables public. This change follows in the steps of the previous changes that made other kernel types' members private. The main motivation behind this is that the Thread class will likely change in the future as emulation becomes more accurate, and letting random bits of the emulator access data members of the Thread class directly makes it a pain to shuffle around and/or modify internals. Having all data members public like this also makes it difficult to reason about certain bits of behavior without first verifying what parts of the core actually use them. Everything being public also generally follows the tendency for changes to be introduced in completely different translation units that would otherwise be better introduced as an addition to the Thread class' public interface.
* arm_interface: Replace kernel vm_manager include with a forward declarationGravatar Lioncash2018-09-201-0/+1
| | | | | | Avoids an unnecessary inclusion and also uncovers three places where indirect inclusions were relied upon, which allows us to also resolve those.
* kernel/mutex: Replace ResultCode construction for invalid addresses with the ↵Gravatar Lioncash2018-09-171-2/+2
| | | | | | | | named variant We already have a ResultCode constant for the case of an invalid address, so we can just use it instead of re-rolling that ResultCode type.
* kernel: Eliminate kernel global stateGravatar Lioncash2018-08-281-3/+3
| | | | | | | | | | | | | | | | | | | | | | As means to pave the way for getting rid of global state within core, This eliminates kernel global state by removing all globals. Instead this introduces a KernelCore class which acts as a kernel instance. This instance lives in the System class, which keeps its lifetime contained to the lifetime of the System class. This also forces the kernel types to actually interact with the main kernel instance itself instead of having transient kernel state placed all over several translation units, keeping everything together. It also has a nice consequence of making dependencies much more explicit. This also makes our initialization a tad bit more correct. Previously we were creating a kernel process before the actual kernel was initialized, which doesn't really make much sense. The KernelCore class itself follows the PImpl idiom, which allows keeping all the implementation details sealed away from everything else, which forces the use of the exposed API and allows us to avoid any unnecessary inclusions within the main kernel header.
* kernel: Move object class to its own source filesGravatar Lioncash2018-08-011-1/+1
| | | | | | General moving to keep kernel object types separate from the direct kernel code. Also essentially a preliminary cleanup before eliminating global kernel state in the kernel code.
* Merge pull request #877 from lioncash/removeGravatar bunnei2018-07-311-1/+0
|\ | | | | kernel: Remove unused object_address_table.cpp/.h
| * kernel: Remove unused object_address_table.cpp/.hGravatar Lioncash2018-07-311-1/+0
| | | | | | | | | | | | These source files were entirely unused throughout the rest of the codebase. This also has the benefit of getting rid of a global variable as well.
* | kernel: Remove unnecessary includesGravatar Lioncash2018-07-311-0/+4
|/ | | | | Removes unnecessary direct dependencies in some headers and also gets rid of indirect dependencies that were being relied on to be included.
* mutex: Pass SharedPtr to GetHighestPriorityMutexWaitingThread() by referenceGravatar Lioncash2018-07-231-1/+1
| | | | | The pointed to thread's members are simply observed in this case, so we don't need to copy it here.
* thread: Convert ThreadStatus into an enum classGravatar Lioncash2018-07-191-3/+3
| | | | | Makes the thread status strongly typed, so implicit conversions can't happen. It also makes it easier to catch mistakes at compile time.
* Kernel/Arbiters: Add stubs for 4.x SignalToAddress/WaitForAddres SVCs.Gravatar Michael Scire2018-06-211-2/+2
|
* Mutex: Do not assert when the mutex waiting threads list isn't empty on ↵Gravatar Subv2018-05-201-1/+0
| | | | | | mutex release. A thread may own multiple mutexes at the same time, and only release one of them while other threads are waiting for the other mutexes.
* Kernel: Implemented mutex priority inheritance.Gravatar Subv2018-04-231-8/+31
| | | | | | | Verified with a hwtest and implemented based on reverse engineering. Thread A's priority will get bumped to the highest priority among all the threads that are waiting for a mutex that A holds. Once A releases the mutex and ownership is transferred to B, A's priority will return to normal and B's priority will be bumped.
* Kernel: Remove old and unused Mutex code.Gravatar Subv2018-04-201-120/+0
|
* Kernel: Corrected the implementation of svcArbitrateLock and svcArbitrateUnlock.Gravatar Subv2018-04-201-0/+94
| | | | | | | | | | Switch mutexes are no longer kernel objects, they are managed in userland and only use the kernel to handle the contention case. Mutex addresses store a special flag value (0x40000000) to notify the guest code that there are still some threads waiting for the mutex to be released. This flag is updated when a thread calls ArbitrateUnlock. TODO: * Fix svcWaitProcessWideKey * Fix svcSignalProcessWideKey * Remove the Mutex class.
* mutex: Update hasWaiters on release.Gravatar bunnei2018-02-051-0/+1
|
* mutex: Remove unused call to VerifyGuestState.Gravatar bunnei2018-01-081-3/+0
|
* Kernel: Properly keep track of mutex lock data in the guest memory. This ↵Gravatar Subv2018-01-081-54/+43
| | | | fixes userland locking/unlocking.
* svc: Implement svcLockMutex.Gravatar bunnei2018-01-011-18/+63
|
* Merge remote-tracking branch 'upstream/master' into nxGravatar bunnei2017-10-091-2/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | # Conflicts: # src/core/CMakeLists.txt # src/core/arm/dynarmic/arm_dynarmic.cpp # src/core/arm/dyncom/arm_dyncom.cpp # src/core/hle/kernel/process.cpp # src/core/hle/kernel/thread.cpp # src/core/hle/kernel/thread.h # src/core/hle/kernel/vm_manager.cpp # src/core/loader/3dsx.cpp # src/core/loader/elf.cpp # src/core/loader/ncch.cpp # src/core/memory.cpp # src/core/memory.h # src/core/memory_setup.h
| * Fixed type conversion ambiguityGravatar Huw Pascoe2017-09-301-1/+1
|/
* Kernel/Mutex: Propagate thread priority changes to other threads inheriting ↵Gravatar Subv2017-01-041-38/+22
| | | | the priority via mutexes
* Kernel/Mutex: Update a mutex priority when a thread stops waiting on it.Gravatar Subv2017-01-041-13/+22
|
* Kernel/Mutex: Implemented priority inheritance.Gravatar Subv2017-01-041-13/+45
| | | | | | | The implementation is based on reverse engineering of the 3DS's kernel. A mutex holder's priority will be temporarily boosted to the best priority among any threads that want to acquire any of its held mutexes. When the holder releases the mutex, it's priority will be boosted to the best priority among the threads that want to acquire any of its remaining held mutexes.
* Kernel: Object ShouldWait and Acquire calls now take a thread as a parameter.Gravatar Subv2017-01-041-18/+6
| | | | This will be useful when implementing mutex priority inheritance.
* Kernel/Synch: Do not attempt a reschedule on every syscall.Gravatar Subv2017-01-041-0/+1
| | | | Not all syscalls should cause reschedules, this commit attempts to remedy that, however, it still does not cover all cases.
HIC SVNT DRACONES