8259825: Find a better way to detect Metal framework availability on system #212
Conversation
|
@aghaisas 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 no new commits pushed to the
|
This only downside of this is that it will be no longer possible to run the Metal pipeline on macOS 10.13 systems. Since Apple no longer supports macOS 10.13, this is probably fine, but I recommend waiting to integrate this until @prrace approves it. |
I have raised this PR now as a response to the review comment at openjdk/jdk#2403 (comment) |
Probably a good thing to make this policy change before integration.
I don't see metal as important for 10.13 systems anyway.
/integrate |
@aghaisas Since your change was applied there have been 16 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit d729f30. |
Issue :
In Lanai code-base, system profiler command was used to detect Metal framework availability. This implementation although works as expected, is slower.
Fix :
I have replaced the logic that was using system profiler command with @available check for macOS Mojave (10.14)
More Info :
https://support.apple.com/en-us/HT205073 - mentions the HW that supports Metal framework. It is practically difficult to detect HW and then decide whether Metal framework is supported or not.
Instead, it is appropriate to check for OS version that guarantees Metal framework availability.
Please refer - https://support.apple.com/en-us/HT208898 - It is mentioned in the first line @ this link that "macOS Mojave requires a graphics card that supports Metal"
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/lanai pull/212/head:pull/212
$ git checkout pull/212