1. 13 Mar, 2019 2 commits
    • Lioncash's avatar
      core/hle/kernel/svc: Implement svcMapTransferMemory · 567134f8
      Lioncash authored
      Now that transfer memory handling is separated from shared memory, we
      can implement svcMapTransferMemory pretty trivially.
      567134f8
    • Lioncash's avatar
      core/hle/kernel: Split transfer memory handling out into its own class · cb198d79
      Lioncash authored
      Within the kernel, shared memory and transfer memory facilities exist as
      completely different kernel objects. They also have different validity
      checking as well. Therefore, we shouldn't be treating the two as the
      same kind of memory.
      
      They also differ in terms of their behavioral aspect as well. Shared
      memory is intended for sharing memory between processes, while transfer
      memory is intended to be for transferring memory to other processes.
      
      This breaks out the handling for transfer memory into its own class and
      treats it as its own kernel object. This is also important when we
      consider resource limits as well. Particularly because transfer memory
      is limited by the resource limit value set for it.
      
      While we currently don't handle resource limit testing against objects
      yet (but we do allow setting them), this will make implementing that
      behavior much easier in the future, as we don't need to distinguish
      between shared memory and transfer memory allocations in the same place.
      cb198d79
  2. 12 Mar, 2019 3 commits
  3. 10 Mar, 2019 9 commits
  4. 09 Mar, 2019 7 commits
  5. 08 Mar, 2019 11 commits
  6. 07 Mar, 2019 8 commits