Tpetra: Don't test need_sync_[host|device] #13833
Open
+0
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@trilinos/tpetra
Motivation
kokkos/kokkos#7775 proposes to skip
modify
andsync
ifDualView
only references oneView
, i.e., if the memory space is host-accessible. This changes the behavior ofDualView::need_sync_[host|device]
and thusTpetra::MultiVector::need_sync_[host|device]
which just calls the respectiveDualView
function, seeTrilinos/packages/tpetra/core/src/Tpetra_MultiVector_def.hpp
Lines 4494 to 4506 in 74d6091
Tpetra
unit tests checks this behavior explicitly and therefore breaks with kokkos/kokkos#7775.This pull request proposes to just remove this particular check since the
MultiVector
function only forwards anyway.An alternative would be to use
once
Kokkos
is updated inTrilinos
.Testing
Running all
Tpetra
unit tests with a configuration that hasKokkos_ENABLE_CUDA_UVM=ON
.