Skip to content
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

another single pe becomes occupied even though only a single pe is opened. #95

Closed
hyunsik opened this issue Jul 20, 2023 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@hyunsik
Copy link
Member

hyunsik commented Jul 20, 2023

Problem

Even though we open only a single pe, the remaining single pe becomes OCCUPIED state.

How to reproduce

>>> config = DeviceConfig(arch=Arch.Warboy, mode=DeviceMode.Single, count=2)
>>> find_device_files(config)
[npu0pe0, npu0pe1]
>>> config = DeviceConfig(arch=Arch.Warboy, mode=DeviceMode.Single, count=1)
>>> find_device_files(config)
[npu0pe0]
>>> pe0 = open("/dev/npu0pe0")
>>> find_device_files(config)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: Device warboy(1)*1 not found
@hyunsik hyunsik added the bug Something isn't working label Jul 20, 2023
yw-furiosa added a commit to yw-furiosa/device-api that referenced this issue Jul 21, 2023
yw-furiosa added a commit to yw-furiosa/device-api that referenced this issue Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant