Skip to content

POC for zelUnloadDrivers - #502

Draft
rwmcguir wants to merge 2 commits into
oneapi-src:masterfrom
rwmcguir:russ_poc_zelUnloadDriver
Draft

POC for zelUnloadDrivers#502
rwmcguir wants to merge 2 commits into
oneapi-src:masterfrom
rwmcguir:russ_poc_zelUnloadDriver

Conversation

@rwmcguir

@rwmcguir rwmcguir commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

POC Only for design discussion, not for merging yet.
May need to be moved to L0 Spec discssuion

At current drivers unloaded, cannot be reloaded due to initial implementation. This is the first major limitation in this design. A design decision needs to be made here, if we support re-loading, or effectively treat this as a banned driver during this process execution.

Driver ordering is impacted, not re-ordering but a HOLE will develop in the schema, so if N devices loaded, and N-1 devices are left, it would not be clear to user which N's are valid. It appears very unsafe to attempt re-ordering after users may have driver handles, so list compaction seems like a bad idea. Returning UNITIALIZED seems best for now, or in the future UNLOADED is a potential upgrade. This specifically affects zer* API's if the first driver is unloaded, they will then be redirected to the next valid driver.

rwmcguir added 2 commits July 31, 2026 16:23
Signed-off-by: Russell McGuire <russell.w.mcguire@intel.com>
+ Thus the zelUnloadDriver is a oneshot

Signed-off-by: Russell McGuire <russell.w.mcguire@intel.com>
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.

1 participant