You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
f2331a804a
00336
02751
Kernel
Update-some-barriers-test
astc_optimization1
astc_optimizations
atomic-wait-fence-mode
atomicops-mxwell
bcn-ternary-soft
camillelavey-patch-1
chore/chore
civa
cyber/async-gpu-android
descriptor
descriptor_pool_opt
descriptor_set
discfix
dmnt2
dravee/remove-async
dynarmic-ppc64
eden-orbis-ps4
eds-true-adreno-fixes
eds-true-adreno-fixes-pre-0.1.0
feat/android_kotlin_compose
feat/game_override
feat/new_lang
ffmpeg-cross-compile
fix/discord-rpc
fix/socket
flatopsfixes23485
fs-try
gpuopts
interval-zero
lanobu
liz-crash-dumps-solaris
liz-dynarmic-macos-fbsd-port
liz-get-rid-of-mcl-intrusive-list
liz-heaptrack-fix
lizzie/adreno5-mali-driver-fix
lizzie/astc-mp4-improv
lizzie/audio-remove-recursive-lock
lizzie/correcter-convert-abgr8-srgb-d24s8
lizzie/dynarmic-sse3-impls
lizzie/dynrregabiset
lizzie/evil-f32-u32-format-fix
lizzie/fix-dragonslayer-armnce
lizzie/fix-my-fuckup-with-vic
lizzie/fix-rw-garten
lizzie/fix-vic-msvc-attempt-2
lizzie/gmake-fix
lizzie/gutter-sw-blitter
lizzie/inline-dynarmic-spooky
lizzie/ios-port-sud
lizzie/ltofix123
lizzie/macos-fix
lizzie/macos-vk-metal-fix-stype
lizzie/maxwell-dumb-tools
lizzie/nce-port1123
lizzie/qt-fix-user-dialogue
lizzie/rasterizer-recursive-mutex-not
lizzie/remove-disassembler-dynarmic
lizzie/rework-block-list
lizzie/settings-blocked-domains
lizzie/sgsr
lizzie/splay
lizzie/spscs-mpscs-queue
lizzie/stupid-socket-bullshit
lizzie/texture-pass-revert-1
lizzie/thai-polish
lizzie/try-fix-win11-crash-fuck
lizzie/vids-ratatata
lizzie/xbyak-unor-mapfix-with-boost
lock-term-1
macroify-surface-stuffs
master
mmap-fixews
msvc
mutliplayer-filter-better1
n64
nce_cpp
pipelinederivative
qcomopts2
querybugfix
refactoreds2
release-early-fences
release/0.0.3
release/0.0.4
release/0.1.0
renderer_vulkan
revert-2695
revert-noinline
revert-xbyak
revertrevert
sgsrtry
showcase
showcase2
sjkdbsdfjkbsdf-2834
spvopts
sured-revert
techno48473719
test-revert-gpu-optim
test2
true-eds
true-eds-graphics
true-eds-pre-0.0.1
uma
vk-fix-oom-force-maller-buffers
vk-surface-andpc
vk-symph
vkexperiments1
vuid00336_1
vuid02999
vuid04553
vulkan-thingy
vulkanasync
woa-turnip-expr
workgroup
xbzk-msvc-C4127-fix-2
xbzk-saf-recursive-write-with-permission-request
xbzk/bindless-textures-support
xbzk/dma-step-ondemand-flush
xbzk/feat_single_game_folder_external_content_loader
xbzk/flicker-fix
xbzk/vulkan-vuid-goodies-pack
0.0.0
0.0.1-pre-alpha
0.0.2-pre-alpha
test-tag1
test-tag2
v0.0.3
v0.0.3-rc1
v0.0.3-rc2
v0.0.3-rc3
v0.0.3.git
v0.0.4
v0.0.4-rc1
v0.0.4-rc2
v0.0.4-rc2.test
v0.0.4-rc2.test2
v0.0.4-rc3
v0.0.4-rc3.test1
v0.0.4-rc3.test2
v0.0.4.test
v0.1.0
v0.1.0-rc1
v0.1.1
v0.2.0-rc1
${ noResults }
eden/.appveyor
Our initialization process is a little wonky than one would expect when
it comes to code flow. We initialize the CPU last, as opposed to
hardware, where the CPU obviously needs to be first, otherwise nothing
else would work, and we have code that adds checks to get around this.
For example, in the page table setting code, we check to see if the
system is turned on before we even notify the CPU instances of a page
table switch. This results in dead code (at the moment), because the
only time a page table switch will occur is when the system is *not*
running, preventing the emulated CPU instances from being notified of a
page table switch in a convenient manner (technically the code path
could be taken, but we don't emulate the process creation svc handlers
yet).
This moves the threads creation into its own member function of the core
manager and restores a little order (and predictability) to our
initialization process.
Previously, in the multi-threaded cases, we'd kick off several threads
before even the main kernel process was created and ready to execute (gross!).
Now the initialization process is like so:
Initialization:
1. Timers
2. CPU
3. Kernel
4. Filesystem stuff (kind of gross, but can be amended trivially)
5. Applet stuff (ditto in terms of being kind of gross)
6. Main process (will be moved into the loading step in a following
change)
7. Telemetry (this should be initialized last in the future).
8. Services (4 and 5 should ideally be alongside this).
9. GDB (gross. Uses namespace scope state. Needs to be refactored into a
class or booted altogether).
10. Renderer
11. GPU (will also have its threads created in a separate step in a
following change).
Which... isn't *ideal* per-se, however getting rid of the wonky
intertwining of CPU state initialization out of this mix gets rid of
most of the footguns when it comes to our initialization process.
|
7 years ago | |
|---|---|---|
| .. | ||
| UtilityFunctions.ps1 | Implement Citra pull 3043 | 8 years ago |