Skip to content

Recognize POWER11 and future coverage on AIX - #7522

Merged
babsingh merged 1 commit into
eclipse-omr:masterfrom
zl-wang:master
Nov 5, 2024
Merged

Recognize POWER11 and future coverage on AIX#7522
babsingh merged 1 commit into
eclipse-omr:masterfrom
zl-wang:master

Conversation

@zl-wang

@zl-wang zl-wang commented Nov 4, 2024

Copy link
Copy Markdown
Contributor

POWER11 recognition macro is defined before it is officially available from AIX system header files. A catch-all macro for future processors is defined as well.

@zl-wang
zl-wang requested a review from babsingh as a code owner November 4, 2024 14:58
@zl-wang

zl-wang commented Nov 4, 2024

Copy link
Copy Markdown
Contributor Author

@dsouzai please review/approve/merge

@dsouzai

dsouzai commented Nov 5, 2024

Copy link
Copy Markdown
Contributor

jenkins build all

@dsouzai dsouzai self-assigned this Nov 5, 2024
Comment thread port/unix/omrsysinfo.c Outdated
Comment thread port/unix/omrsysinfo.c
Comment thread port/unix/omrsysinfo.c
Comment on lines +1197 to +1199
} else if (__power_latestKnownAndUp()) {
desc->processor = OMR_PROCESSOR_PPC_P11;

@babsingh babsingh Nov 5, 2024

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this change incorrectly mark Power12+ processors as Power11 once newer versions are introduced, leading the API to provide misleading information? Wouldn't using OMR_PROCESSOR_PPC_UNKNOWN be a better and more accurate alternative instead of providing incorrect information?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can refer as pFuture ... the naming cannot be used until IBM uses it publicly, in case IBM changes the naming.
OMR_PROCESSOR_PPC_UNKNOWN is exactly the wrong thing to do here. __power_latestKnownAndUp() was exactly defined to address this existing problem: OMR_PROCESSOR_PPC_UNKNOWN makes us not able to exploit processor features (we are forced to using common set of ISA from 25 years ago). this fix at least allows us to use features available in POWER11.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Once Power12 or pFuture is introduced, we will have to update it again. Do we have an issue open to track follow up changes to this method? If not, we should open one and link it to this PR; it will make it easy to track future work.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

given IBM Infrastructure currently expected cadence of POWER processor refresh, it will be a long-drawn-out issue (we can discuss the details offline). Furthermore, we will naturally be required to do it by our main runtime stakeholder anyway.

Comment thread port/unix/omrsysinfo.c Outdated
Comment thread port/unix/omrsysinfo.c
Comment on lines +1197 to +1199
} else if (__power_latestKnownAndUp()) {
desc->processor = OMR_PROCESSOR_PPC_P11;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Once Power12 or pFuture is introduced, we will have to update it again. Do we have an issue open to track follow up changes to this method? If not, we should open one and link it to this PR; it will make it easy to track future work.

POWER11 recognition macro is defined before it is officially
available from AIX system header files. A catch-all macro for
future processors is defined as well.

Signed-off-by: Julian <zlwang@ca.ibm.com>
@babsingh

babsingh commented Nov 5, 2024

Copy link
Copy Markdown
Contributor

jenkins build all

@babsingh
babsingh merged commit aeffcb5 into eclipse-omr:master Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants