diff options
| author | Kevin Sala <kevin.sala@bsc.es> | 2023-01-25 01:04:07 +0100 |
|---|---|---|
| committer | Kevin Sala <kevin.sala@bsc.es> | 2023-02-06 10:09:35 +0100 |
| commit | 6ca034644d59dde3e00c1a41196bb9ba44bc1b17 (patch) | |
| tree | 78e64d1fc6ea2c9ee272faace531809e2d289d9b /llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp | |
| parent | 80eacb1bc21f185ee62814e302c135cadbf1d26c (diff) | |
| download | llvm-6ca034644d59dde3e00c1a41196bb9ba44bc1b17.zip llvm-6ca034644d59dde3e00c1a41196bb9ba44bc1b17.tar.gz llvm-6ca034644d59dde3e00c1a41196bb9ba44bc1b17.tar.bz2 | |
[OpenMP][libomptarget] Notify the plugins regarding new mapping/unmappings
The NextGen plugins use the information regarding new mapping/unmappings to
lock/unlock the corresponding host buffer and speed up the host-device memory
transfers involving those buffers. The locking/unlocking is disabled by default
and can be enabled by the LIBOMPTARGET_LOCK_MAPPED_HOST_BUFFERS envar. The
envar accepts boolean values (on/off) and a special option:
- off: Do not lock mapped host buffers (default).
- on: Lock mapped host buffers automatically, but do not report lock
failures if the plugin fails to lock them.
- mandatory: Lock mapped host buffers automatically and treat locking failures
in the plugins as fatal errors. This option may be useful for
debugging purposes.
Differential Revision: https://reviews.llvm.org/D142514
Diffstat (limited to 'llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions