1. 30 Mar, 2019 2 commits
    • Lioncash's avatar
      service/fatal: Remove unnecessary semicolon · 11505d3d
      Lioncash authored
      Resolves a -Wextra-semi warning.
      11505d3d
    • Lioncash's avatar
      service/fatal: Name FatalInfo structure members · cc737e58
      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.
      cc737e58
  2. 29 Mar, 2019 2 commits
  3. 28 Mar, 2019 3 commits
  4. 27 Mar, 2019 8 commits
  5. 26 Mar, 2019 4 commits
  6. 24 Mar, 2019 11 commits
    • Lioncash's avatar
      core/cheat_engine: Make MemoryReadImpl and MemoryWriteImpl internally linked · b26481c9
      Lioncash authored
      These don't need to be visible outside of the translation unit, so they
      can be enclosed within an anonymous namespace.
      b26481c9
    • Lioncash's avatar
      core/core_timing: Make callback parameters consistent · c5d41fd8
      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.
      c5d41fd8
    • Lioncash's avatar
      kernel/kernel: Remove unnecessary forward declaration · bd7ec1a7
      Lioncash authored
      This is no longer necessary, as ResultVal isn't used anywhere in the
      header.
      bd7ec1a7
    • Lioncash's avatar
      kernel/process: Remove unused AddressMapping struct · 7c4bc7b8
      Lioncash authored
      Another leftover from citra that's now no longer necessary.
      7c4bc7b8
    • Lioncash's avatar
      kernel/vm_manager: Handle shrinking of the heap size within SetHeapSize() · 1e92ba27
      Lioncash authored
      One behavior that we weren't handling properly in our heap allocation
      process was the ability for the heap to be shrunk down in size if a
      larger size was previously requested.
      
      This adds the basic behavior to do so and also gets rid of HeapFree, as
      it's no longer necessary now that we have allocations and deallocations
      going through the same API function.
      
      While we're at it, fully document the behavior that this function
      performs.
      1e92ba27
    • Lioncash's avatar
      kernel/vm_manager: Rename HeapAllocate to SetHeapSize · 99a16347
      Lioncash authored
      Makes it more obvious that this function is intending to stand in for
      the actual supervisor call itself, and not acting as a general heap
      allocation function.
      
      Also the following change will merge the freeing behavior of HeapFree
      into this function, so leaving it as HeapAllocate would be misleading.
      99a16347
    • Lioncash's avatar
      kernel/vm_manager: Handle case of identical calls to HeapAllocate · abdb81cc
      Lioncash authored
      In cases where HeapAllocate is called with the same size of the current
      heap, we can simply do nothing and return successfully.
      
      This avoids doing work where we otherwise don't have to. This is also
      what the kernel itself does in this scenario.
      abdb81cc
    • Lioncash's avatar
      kernel/vm_manager: Remove unused class variables · 9f63acac
      Lioncash authored
      Over time these have fallen out of use due to refactoring, so these can
      be removed.
      9f63acac
    • Lioncash's avatar
      kernel/vm_manager: Remove unnecessary heap_used data member · 52980df1
      Lioncash authored
      This isn't required anymore, as all the kernel ever queries is the size
      of the current heap, not the total usage of it.
      52980df1
    • Lioncash's avatar
      kernel/vm_manager: Tidy up heap allocation code · 586cab61
      Lioncash authored
      Another holdover from citra that can be tossed out is the notion of the
      heap needing to be allocated in different addresses. On the switch, the
      base address of the heap will always be managed by the memory allocator
      in the kernel, so this doesn't need to be specified in the function's
      interface itself.
      
      The heap on the switch is always allocated with read/write permissions,
      so we don't need to add specifying the memory permissions as part of the
      heap allocation itself either.
      
      This also corrects the error code returned from within the function.
      If the size of the heap is larger than the entire heap region, then the
      kernel will report an out of memory condition.
      586cab61
    • bunnei's avatar
      Merge pull request #2232 from lioncash/transfer-memory · 3f74518e
      bunnei authored
       core/hle/kernel: Split transfer memory handling out into its own class
      3f74518e
  7. 23 Mar, 2019 3 commits
  8. 22 Mar, 2019 7 commits