derek/gem5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gpu-compute: Handle mailbox/wakeup signals for GPUFS

Browse Source 
The current mailbox/wakeup signal uses the SE mode proxy port to write
the event value. This is not available in full system mode so instead we
need to issue a DMA write to the address. The value of event_val clears
the event.

Change-Id: I424469076e87e690ab0bb722bac4c3e7414fb150
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/57709
Reviewed-by: Matt Sinclair <mattdsinclair@gmail.com>
Maintainer: Matt Sinclair <mattdsinclair@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
This commit is contained in:
Matthew Poremba
2022-03-15 09:13:18 -05:00
parent fb173e4d2c
commit 347364ab0f
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/gpu-compute/gpu_command_processor.cc
View File

@@ -224,7 +224,17 @@ GPUCommandProcessor::updateHsaSignal(Addr signal_handle, uint64_t signal_value,
DPRINTF(GPUCommandProc, "Calling signal wakeup event on "
"signal event value %d\n", *event_val);
signalWakeupEvent(*event_val);
// The mailbox/wakeup signal uses the SE mode proxy port to write
// the event value. This is not available in full system mode so
// instead we need to issue a DMA write to the address. The value of
// *event_val clears the event.
if (FullSystem) {
auto cb = new DmaVirtCallback<uint64_t>(function, *event_val);
dmaWriteVirt(mailbox_addr, sizeof(Addr), cb, &cb->dmaBuffer, 0);
} else {
signalWakeupEvent(*event_val);
}
}
}