aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
diff options
context:
space:
mode:
authorJoseph Huber <huberjn@outlook.com>2023-11-30 13:46:52 -0600
committerGitHub <noreply@github.com>2023-11-30 13:46:52 -0600
commit0584e6c1669dbfc6252f5b069e2a895389660120 (patch)
treee8d140fbf42798fe35c6ce56cbae1177daf2f0bb /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
parentbf4a876309cdc73e3907801abba02d2f1d2d7b6e (diff)
downloadllvm-0584e6c1669dbfc6252f5b069e2a895389660120.zip
llvm-0584e6c1669dbfc6252f5b069e2a895389660120.tar.gz
llvm-0584e6c1669dbfc6252f5b069e2a895389660120.tar.bz2
[libc] Explicitly pin memory for the HSA memory transfer (#73973)
Summary: This portion of code handles mapping the RPC client memory over to the device. HSA copies need to be between two slices of memory that HSA has allocated. Previously we used coarse-grained memory to act as the host source. However, the support for this varies depending on the kernel and version and should not be relied upon. This patch changes that handling to use the `hsa_amd_memory_lock` API to explicitly pin memory to a location sufficient for a DMA transfer to the GPU.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions