Skip to content

Conversation

jharlow-intel
Copy link
Contributor

@jharlow-intel jharlow-intel commented Aug 19, 2025

  • Have you provided a meaningful PR description?
  • Have you added a test, reproducer or referred to an issue with a reproducer?
  • Have you tested your changes locally for CPU and GPU devices?
  • Have you made sure that new changes do not introduce compiler warnings?
  • Have you checked performance impact of proposed changes?
  • Have you added documentation for your changes, if necessary?
  • Have you added your changes to the changelog?
  • If this PR is a work in progress, are you opening the PR as a draft?

This PR adds some needed environment variable documentation to the git pages.

Copy link

Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_105 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

@coveralls
Copy link
Collaborator

coveralls commented Aug 19, 2025

Coverage Status

coverage: 85.902%. remained the same
when pulling a25c161 on task/SAT-7838
into a6a0fdd on master.

@jharlow-intel jharlow-intel force-pushed the task/SAT-7838 branch 2 times, most recently from e346c8f to 6ad1f1b Compare August 20, 2025 15:21
Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_105 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_107 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_105 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

1 similar comment
Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_105 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_105 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_105 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

@jharlow-intel
Copy link
Contributor Author

@ndgrigorian ready for another review

@ndgrigorian
Copy link
Collaborator

Noting:
Closes #2037

Variable ``ZE_AFFINITY_MASK``
-------------------------------
Allows users to mask specific devices from being used by SYCL applications.
If we have ZE_FLAT_DEVICE_HIERARCHY set to COMPOSITE, we can have an AFFINITY of “1” for our application to only see device #1 - making system devices 0, and 2+, invisible. Etc.
Copy link
Collaborator

Choose a reason for hiding this comment

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

may be worth mentioning how it works with FLAT and COMBINED
see: https://www.intel.com/content/www/us/en/developer/articles/technical/flattening-gpu-tile-hierarchy.html

I'm not sure if I've tested combined with affinity mask in retrospect...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I already linked that for the ZE_DEVICE_HIERARCHY docs, and I can't find any mention of how exactly ZE_AFFINITY_MASK interacts with COMBINED.

I will include the blurb about FLAT here as well, but I see nothing for COMBINED documented here: https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/PROG.html#affinity-mask

Copy link
Collaborator

Choose a reason for hiding this comment

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

yeah I'm going to go ahead and test it myself, since it's not documented in the compiler composite device extension either

Copy link

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_111 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants