forked from ofiwg/libfabric
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
src/hmem_ze: map device id to physical device
The devices returned from zeDeviceGet map to each subdevice (tile), not physical PCI devices. This means on a system with 2 physical devices, each with 2 tiles, ZE will return 4 devices total. This conflicts with the shm IPC implementation which uses device fds on each physical device. This commit creates a mapping between the devices returned from zeDeviceGet and the physical devices they are on and uses that mapping internally to get the correct device fd for the IPC implementation. This is done by looking at the device domain and PCI bus IDs returned from the device properties (known to be at slots 6 and 8, respectively) and matching it to the domain and bus IsD in the file name opened for the device fd, which is in the format domain:bus:dev.func Signed-off-by: Alexia Ingerson <alexia.ingerson@intel.com>
- Loading branch information
Showing
4 changed files
with
46 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters