-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completely lock-free ClassLoader::LookupTypeKey #61346
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
1b003e3
embedded size
VSadov 5330325
next array
VSadov c5db8c4
read consistency while rehashing
VSadov c264f69
comments
VSadov e8e7d6e
remove CRST_UNSAFE_ANYMODE and COOP mode in the callers
VSadov b9b4813
typo
VSadov 749695a
fix 32bit builds
VSadov 5569c66
couple changes from review.
VSadov 7c3cd08
Walk the buckets in resize.
VSadov f8b1021
remove a `REVIEW:` comment.
VSadov 067cefb
Update src/coreclr/vm/dacenumerablehash.inl
VSadov 1516f6b
remove use of `auto`
VSadov efe6043
DAC stuff
VSadov f455581
Constructor and GrowTable are not called by DAC, no need for DPTR, ad…
VSadov e874b3c
SKIP_SPECIAL_SLOTS
VSadov c7eb7e7
More compact dac_cast in GetNext
VSadov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hoyosjs - If debugger only does lookups, then it will no longer take this look, then
CRST_DEBUGGER_THREAD
is not needed.Can debugger load/publish types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we can't load assemblies, but it's possible that a FuncEval can load a type I believe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is funceval running on debugger thread?
I assumed that
CRST_DEBUGGER_THREAD
does not cover funceaval, since funceval could JIT and JIT does all kind of stuff (including loading assemblies). If that is attributed to the debugger thread, then debugger thread is not different from anything else.I am not very familiar with how that all works though.
CRST_DEBUGGER_THREAD
is not a big nuisance here. I was just not sure it is still necessary.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tried removing
CRST_DEBUGGER_THREAD
and running both regular and diagnostics tests (with Chk bits) - everything runs as before. Not sure if that is enough proof thatCRST_DEBUGGER_THREAD
is unnecessary.I just noticed that
CRST_DEBUGGER_THREAD
is always paired withCRST_UNSAFE_ANYMODE
(or sometimesCRST_GC_NOTRIGGER_WHEN_TAKEN
), so since we are removing the other one, maybe we do not needCRST_DEBUGGER_THREAD
either.But do not think
CRST_DEBUGGER_THREAD
is a big nuisance either way - it basically increments/decrements a counter that is checked in couple asserts.