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
8253015: Aarch64: Move linux code out from generic CPU feature detection #299
Conversation
|
This backport pull request has now been updated with issue from the original commit. |
c55192d
to
4884ef8
Compare
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.
Thanks for taking care of this.
Original change introduced two regressions which were fixed in:
- JDK-8255975: Fix AArch64 OpenJDK build failure with gcc-5 -- but it is not a problem for this change, since
STATIC_ASSERT
is used - JDK-8255716: AArch64: Regression: JVM crashes if manually offline a core -- this is still a problem for this backport
I'm not sure is it better to backport JDK-8255716 separately or, considering that the follow-up change is small, to add that into this change (like adding another commit in the PR and do /issue add
manually as described in https://wiki.openjdk.java.net/display/SKARA/Pull+Request+Commands#PullRequestCommands-/issue)
} | ||
fclose(f); | ||
} | ||
guarantee(cpu_lines == os::processor_count(), "core count should be consistent"); |
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.
This line was later removed in https://bugs.openjdk.java.net/browse/JDK-8255716
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.
Thanks for bringing this to my attention. I added that commit / issue here.
/issue add 8255716 |
@rnkovacs |
/contributor add Bernhard Urban-Forster burban@openjdk.org |
@rnkovacs |
@AntonKozlov Thank you. Could you please tag these two JBS issues for me? |
I would like to, but my review does not count -- I'm not a formal reviewer in the JDK Updates project. |
Right, I'll check out the formal Reviewers list. Thanks. |
Can we get a formal review here please ? |
a06cf59
to
5a2e329
Compare
There's progress on #274 now. I suppose we can get that integrated shortly and then come back here. |
1b4247f
to
08e454f
Compare
Rebase (dependency has been updated). |
The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout 8250810-push-missing
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
08e454f
to
f4b7e65
Compare
Another rebase. |
@theRealAph @TheRealMDoerr Any chance to review this? Would be the next one in the chain for Windows AArch64 port (and I believe required as a prerequisite for Mac Arm64 as well?) |
@theRealAph @TheRealMDoerr ping. This change is needed for the Windows/AArch64 backport can go in. |
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 don't know which hardware features are supported in 11, but the backports looks good to me.
@rnkovacs This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 41 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TheRealMDoerr) but any other Committer may sponsor as well.
|
Thanks! Tagged both issues. |
/integrate |
/sponsor |
Going to push as commit d336b24.
Your commit was automatically rebased without conflicts. |
@RealCLanger @rnkovacs Pushed as commit d336b24. |
Not a clean backport. Differences to the original commit:
src/hotspot/cpu/aarch64/
andsrc/hotspot/os_cpu/linux_aarch64/
are adjusted to cover hardware features supported in JDK 11.static_assert
s need to be replaced withSTATIC_ASSERT
macros invm_version_linux_aarch64.cpp
.vmStructs_jvmci.cpp
,AArch64HotSpotLIRGenerator.java
andGraalHotSpotVMConfig.java
are skipped as they seem to be modifying code added in JDK 14 (JDK-8226222 and JDK-8231973).This is part of the Windows/AArch64 port.
Progress
Issues
Reviewers
Contributors
<burban@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/299/head:pull/299
$ git checkout pull/299
Update a local copy of the PR:
$ git checkout pull/299
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/299/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 299
View PR using the GUI difftool:
$ git pr show -t 299
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/299.diff