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

Map device_id to OV LUID #614

Open
wants to merge 1 commit into
base: ovep-develop
Choose a base branch
from

Conversation

preetha-intel
Copy link

Description

Add support for passing LUID via device_id provider option and map it with appropriate GPU device using OV get_property

@MayureshV1
Copy link

MayureshV1 commented Mar 11, 2025

@preetha-intel . Can you please capture usage of this feature in the description on how to pass in the LUID.
For e.g.: onnxruntime_Perf_test cmd line.

if (device_name == "No_match_found") {
ORT_THROW(" [ERROR] [OpenVINO] Invalid LUID. No matching hardware is found");
} else {
pi.device_type = device_name;

Choose a reason for hiding this comment

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

What happens when user provides a "device_type" and "device_id" that are mismatching?
For example, the user passes "device_type" as "CPU" and
"device_id" as the "LUID of a valid GPU"

Choose a reason for hiding this comment

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

Expected behavior should be, the LUID would be only checked for expected device_type.
So, in the above example CPU LUID either would not exist or will not match with LUID provided in device_id. Execution should error out saying "Device_Id not found in device_type- CPU."

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