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:
4ed697697d
2ndAdjustmentVulkanV3-STOP_FORCE_PUSHING_CAMILLE
2ndAdjustmentVulkanv2
2ndgpuopts
John-android-rescale-toggle
TTYD
Update-some-barriers-test
android-meows
bcn-ternary-soft
bioshock
blit-fixes
bump-httplib-minver
camile/wawawawa
civa
crueter-patch-1
crueter-patch-3
crueter-patch-4
descriptor_set
dmnt2
dynarmic
dynarmic-ppc64
eden-managarm
eden-orbis-ps4
eden-wasm
ext-boost
feat/android_kotlin_compose
feat/game_override
fix-cpmutil-win
fix-crash-quick-settings
fix-friend-list-freeze
fix-grid-autoalign
fix-update-android
flatopsfixes23485
fs-try
funny-meows
kosmickrisp
launch-games-qlaunch-23
liz-heaptrack-fix
lizzie/1st-anniversary-icon
lizzie/adjust-stream-buffer
lizzie/adl-fix-remove
lizzie/anv-cached-mesa-hack
lizzie/areafixnvidia
lizzie/better-mscxr
lizzie/brunofix7546847
lizzie/bump-18-version-cache
lizzie/clang-fix-gixel
lizzie/cleanup-dynarmic-cmake
lizzie/debug-assert-demote-dynarmic
lizzie/docs-lz12
lizzie/dynarmic-coalesce-rw
lizzie/dynarmic-exclusive-fixups
lizzie/eh-signed
lizzie/fbsd-shm_create_largepage
lizzie/ffmpeg-fix-externel
lizzie/fix-nro-homebrew-noinit-channel
lizzie/fix-nvmap-handles
lizzie/fxaa-123
lizzie/hbloader-fix
lizzie/inline-audio-structure-parent-refs
lizzie/inlinecodecnvenc
lizzie/invert-gyro
lizzie/ios-port-sud
lizzie/jamboree-audio-crash
lizzie/joycon-revision
lizzie/legacy-build-a6
lizzie/lto-fafaf-test-123
lizzie/macos-network-ifaces
lizzie/marknocore
lizzie/mlp223
lizzie/mouse-constrain-fix
lizzie/nce-invalidate-split
lizzie/netbsdgcc14-fix
lizzie/noexcept-dynarmic
lizzie/non-english-policy
lizzie/nuke-cubeb-2
lizzie/nuke-oboe
lizzie/nuke-ssl
lizzie/pixelphonefix
lizzie/pkza-mwait
lizzie/pokemon-search-fix
lizzie/powerunswizzle
lizzie/product-model-wawa
lizzie/rdynr
lizzie/refactor-networking-12
lizzie/remove-disassembler-dynarmic
lizzie/remove-memcpy-on-vector
lizzie/remove-non-ssl-backends
lizzie/remove-vector-math-unused
lizzie/sdl-nuke-SDL_Vibration-thread
lizzie/simplify-invalid-acc
lizzie/ssaa-what-the-fuck
lizzie/stable-shader-pools
lizzie/swkbd-mhu
lizzie/thread-names-log
lizzie/tryfixrandomvkshit
lizzie/ulaunch-attempt1
lizzie/unaligned-attempt-2
lizzie/usepoolinstdynarm
lizzie/vk-ext-fault-info
lizzie/vkweep12
lizzie/wstring-uni-123
lizzie/xcode-evil-shit-123
lsfg-android
lsfg-cleanup
macroify-surface-stuffs
master
memory_changes
mmap-fixews
mutliplayer-filter-better1
n64
pr-template-v2
qlaunch-android
querybugfix
release/0.0.3
release/0.0.4
release/0.1.0
release/0.2.0
restore-metal-surface
return-bruno-fix-2
sjkdbsdfjkbsdf-2834
temporary-branch
tiled-gpu
tiled-gpu-v2
unified-memory-access
update-deps-1780370490
update-deps-1780370770
update-translations-1777730513
update-translations-1788192077
vk-experiments5
vk-experiments7
vk-experiments8
warp-fixes
xbzk/bundled-application-program-IDs-fix
xbzk/fragmented-storage-buffers
xbzk/hb-tico-support-part-2
xbzk/opus-proper-limit-and-error
xbzk/unreal-unsafe-junk-guards
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
v0.2.0-rc1
v0.2.0-rc2
v0.2.1
${ noResults }
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. |
8 years ago | |
|---|---|---|
| .. | ||
| default | Add Dark theme, Icon theming | 9 years ago |
| qdarkstyle | Port #3769 from Citra: "Update Dark theme to latest version" | 8 years ago |