8387381: RISC-V: assert failed with fastdebug build on systems with different core types#31717
Open
zifeihan wants to merge 1 commit into
Open
8387381: RISC-V: assert failed with fastdebug build on systems with different core types#31717zifeihan wants to merge 1 commit into
zifeihan wants to merge 1 commit into
Conversation
… build on systems with different core types
|
👋 Welcome back gcao! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
|
The total number of required reviews for this PR has been set to 2 based on the presence of this label: |
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
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.
HI, Can you help to review this patch? Thanks!
Here is a crash with a fastdebug build on SpacemiT Key Stone K3, which has different core types.
On systems with different core types, the kernel hwprobe syscall returns (uint64_t)-1 as value for MARCHID/MIMPID when CPUs disagree[1]. RVNonExtFeatureValue uses the same -1 as its internal sentinel (DEFAULT_VALUE), so enable_feature(-1) hits the assert.
SpacemiT Key Stone K3 has X100 (marchid=0x8000000058000002) and A100 (marchid=0x8000000041000002) cores, querying all CPUs gives marchid=-1 and mimpid=-1.
Fix: use a separate bool _enabled flag instead of the sentinel value.
[1] https://docs.kernel.org/arch/riscv/hwprobe.html
Testing
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31717/head:pull/31717$ git checkout pull/31717Update a local copy of the PR:
$ git checkout pull/31717$ git pull https://git.openjdk.org/jdk.git pull/31717/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 31717View PR using the GUI difftool:
$ git pr show -t 31717Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31717.diff
Using Webrev
Link to Webrev Comment