Add clarification on why we must take GuestSharedMemory::lock #178
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
syntactically
requested review from
danbugs,
dblnz,
ludfjig and
simongdavies
and removed request for
ludfjig
syntactically
force-pushed
the
lm/shmem-comments
branch
from
7f9a431 to
ed31240
Compare
ludfjig
approved these changes
Jan 28, 2025
Previously, the code comments were not sufficiently clear as to why apparently-useless locks during the execution of the guest are necessary for the invariants of the GuestSharedMemory/HostSharedMemory split. This led to confusion as to whether it would be a good idea to remove them, so this commit clarifies that there is a good reason for them to be there. Signed-off-by: Lucy Menon <[email protected]>
syntactically
force-pushed
the
lm/shmem-comments
branch
from
ed31240 to
b9c67fb
Compare
danbugs
approved these changes
Jan 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, the code comments were not sufficiently clear as to why apparently-useless locks during the execution of the guest are necessary for the invariants of the GuestSharedMemory/HostSharedMemory split. This led to confusion as to whether it would be a good idea to remove them, so this commit clarifies that there is a good reason for them to be there.