-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8367780: Enable UseAPX on Intel CPUs only when both APX_F and APX_NCI_NDD_NF cpuid features are present #27320
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
Conversation
…_NDD_NF cpuid features are present
|
👋 Welcome back sparasa! A progress list of the required criteria for merging this PR into |
|
@vamsi-parasa This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. 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 67 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. ➡️ To integrate this PR with the above commit message to the |
|
@vamsi-parasa The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
|
|
||
| if (!UseAPX) { | ||
| _features.clear_feature(CPU_APX_F); | ||
| _features.clear_feature(CPU_APX_NCI_NDD_NF); |
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.
We don't need separate CPU_APX_NCI_NDD_NF feature and the related changes as CPU_APX_F feature is set only when both bits (sefsl1_cpuid7_edx.bits.apx_f and std_cpuid29_ebx.bits.apx_nci_ndd_nf) are set.
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.
Please see the updated changes which removes CPU_APX_NCI_NDD_NF as an explicit feature.
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.
Looks good to me.
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 answering my questions.. things we checked:
- double-checked reg parameter values of cpuid against the spec
- double-checked endianness of bitset variables in C grammar
- double-checked how offset to the field std_cpuid29_ebx is computed
Change looks good to me
| if (sefsl1_cpuid7_edx.bits.apx_f != 0 && | ||
| xem_xcr0_eax.bits.apx_f != 0) { | ||
| xem_xcr0_eax.bits.apx_f != 0 && | ||
| std_cpuid29_ebx.bits.apx_nci_ndd_nf != 0) { |
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.
was confused why the previous implementation was 'wrong'.. Please clarify that this was triggered "because" of the update to the spec (in the PR description).
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.
Please see the updated PR description which clarifies that this PR was triggered because of the update to the Intel APX spec.
Thanks Vlad for going through the changes and reviewing the PR! |
|
/integrate |
|
Going to push as commit 3d4e049.
Your commit was automatically rebased without conflicts. |
|
@vamsi-parasa Pushed as commit 3d4e049. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
/label add hotspot-compiler-dev |
|
@jatin-bhateja The command |
|
Hi @vamsi-parasa , Before this PR, we could validate APX support using the publicly available latest version 9.58 of Intel software development emulator. After this PR, UseAPX support is false. I think we should delay upstreaming any new feature support until SDE rolls out the support. Best Regards, |
Hi Jatin, Thank for informing about this issue! Thanks, |
Thanks @vamsi-parasa, BTW, there should not be any urgency to push a patch for future enhancement in the absence of software emulation :-) |
|
/backport openjdk/jdk25u |
|
@vamsi-parasa the backport was successfully created on the branch backport-vamsi-parasa-3d4e0491-master in my personal fork of openjdk/jdk25u. To create a pull request with this backport targeting openjdk/jdk25u:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk25u: |
The goal of this PR is to enable APX on Intel CPUs (i.e. enable UseAPX) only when both the APX_F and APX_NCI_NDD_NF cpuid feature flags are present.
The latest update to the Intel APX specification (https://www.intel.com/content/www/us/en/content-details/861610/intel-advanced-performance-extensions-intel-apx-architecture-specification.html ) has changed how APX features are detected on Intel CPUs. Because of this change, we need to update how the JVM enumerates CPU features.
As per the new update, when APX_F is set, processors also provide CPUID leaf 0x29 (APX Advanced Performance Extensions Leaf). Any Intel processor that enumerates APX_F also enumerates APX_NCI_NDD_NF.
This PR enhances the HotSpot x86 CPU feature detection to recognize the APX_NCI_NDD_NF sub-feature of Intel APX and update the enabling logic for UseAPX VM flag.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27320/head:pull/27320$ git checkout pull/27320Update a local copy of the PR:
$ git checkout pull/27320$ git pull https://git.openjdk.org/jdk.git pull/27320/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27320View PR using the GUI difftool:
$ git pr show -t 27320Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27320.diff
Using Webrev
Link to Webrev Comment