A backup of the Yuzu mainline repo. Only includes the master branch, nothing else. https://git.benis.co.uk/yuzu-mainline/atom?h=master 2021-01-01T11:34:38+00:00 2021-01-01T11:34:38+00:00 MerryMage MerryMage@users.noreply.github.com 2021-01-01T11:30:30+00:00 urn:sha1:6d30745d772c7e332bbea1462a92033386b85b08 2020-04-17T04:59:33+00:00 bunnei bunneidev@gmail.com 2020-04-09T02:19:42+00:00 urn:sha1:d95ceaa8ec7a5f3a16ffe3c16cb522a2fad5c746 2019-11-27T02:53:34+00:00 Lioncash mathew1800@gmail.com 2019-11-26T18:09:12+00:00 urn:sha1:323680e5ad3ca0e27f2dd1de26816741b3243bed Migrates all of the direct mapping facilities over to the new memory class. In the process, this also obsoletes the need for memory_setup.h, so we can remove it entirely from the project. 2019-06-10T04:28:33+00:00 Zach Hilman zachhilman@gmail.com 2019-06-10T04:28:33+00:00 urn:sha1:fc0bf91a969cddeb2f84c3e7c3a862fe98f1d438 This allows kernel internal type processes to be assigned IDs in the KIP range while userland processes are assigned in the user range. 2019-04-07T05:12:54+00:00 Lioncash mathew1800@gmail.com 2019-04-07T05:10:44+00:00 urn:sha1:e779686a7618e1db4b1afe0321289ebe3b58aaa8 Centralizes the page table switching to one spot, rather than making calling code deal with it everywhere. 2019-03-17T02:05:40+00:00 bunnei bunneidev@gmail.com 2019-03-02T20:20:28+00:00 urn:sha1:93da8e0abfcdcc6e3cb5488a0db12373429f1377 2019-03-08T04:27:51+00:00 Lioncash mathew1800@gmail.com 2019-03-07T23:48:14+00:00 urn:sha1:8e510d5afa71de2ac5745f461ae3d6156aae803a Now that we have the address arbiter extracted to its own class, we can fix an innaccuracy with the kernel. Said inaccuracy being that there isn't only one address arbiter. Each process instance contains its own AddressArbiter instance in the actual kernel. This fixes that and gets rid of another long-standing issue that could arise when attempting to create more than one process. 2019-03-05T20:47:03+00:00 Lioncash mathew1800@gmail.com 2019-03-05T17:28:10+00:00 urn:sha1:c161389a0f0b0fe3b9d6400c45fd87152f2cb14c Allows getting rid of reliance on the global accessor functions and instead operating on the provided system instance. 2018-10-30T04:03:25+00:00 Frederic L frederic.laing.development@gmail.com 2018-10-30T04:03:25+00:00 urn:sha1:7a5eda59146306dedaf3e6f07f97a8c6898543dd * get rid of boost::optional * Remove optional references * Use std::reference_wrapper for optional references * Fix clang format * Fix clang format part 2 * Adressed feedback * Fix clang format and MacOS build 2018-10-10T06:04:55+00:00 Lioncash mathew1800@gmail.com 2018-10-10T04:42:10+00:00 urn:sha1:5c0408596f6ccf5d2b171321bac386713b169d5b There's no real need to use a shared pointer in these cases, and only makes object management more fragile in terms of how easy it would be to introduce cycles. Instead, just do the simple thing of using a regular pointer. Much of this is just a hold-over from citra anyways. It also doesn't make sense from a behavioral point of view for a process' thread to prolong the lifetime of the process itself (the process is supposed to own the thread, not the other way around).