diff options
| author | Gary Guo <gary@garyguo.net> | 2026-09-01 21:59:32 +0100 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-09-02 10:07:33 +0200 |
| commit | 9e270c4fd863918883977615d7fc54c9b9d018c8 (patch) | |
| tree | 38191778f7dea482dcdaeeb202c7e399c8bf066f /scripts/Makefile.thinlto | |
| parent | b705c185105762676aa6ec16cf976101df87cc35 (diff) | |
| download | linux-next-9e270c4fd863918883977615d7fc54c9b9d018c8.tar.gz linux-next-9e270c4fd863918883977615d7fc54c9b9d018c8.zip | |
gpu: nova-core: fix barrier usage in CPU->GSP messaging path
In the CPU->GSP messaging path, the code reads the read pointer from GSP,
writes the command, advances the write pointer, and then notifies the GSP.
A LOAD->STORE ordering is needed after reading the read pointer from GSP
and writing the command. Control dependency exists here which provide the
needed ordering, but it's best to avoid depending on it.
A STORE->STORE ordering is needed after the command write and before the
write pointer advance. This is currently incorrectly done after the write
pointer advance (and before GSP notification), but this can cause issue if
GSP is still processing ring buffer, as it may observe the write pointer
advance before command write. Thus move this barrier to be before the write
pointer advance. Note that barriers are not needed between write pointer
advance and GSP notification, as MMIO accessors already carries the
required barrier.
Signed-off-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Eliot Courtney <ecourtney@nvidia.com>
Link: https://patch.msgid.link/20260901-rust-barrier-v4-1-94427f445310@garyguo.net
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
