-
Notifications
You must be signed in to change notification settings - Fork 208
NPU plugin support #2066
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
base: main
Are you sure you want to change the base?
NPU plugin support #2066
Conversation
Not tested on real hardware. Development done based on the kernel API and example listings from a real system. |
Supports Core Ultra 1, 2 and 200V series NPUs. Signed-off-by: Tuomas Katila <tuomas.katila@intel.com>
Co-authored-by: Eero Tamminen <eero.t.tamminen@intel.com> Signed-off-by: Tuomas Katila <tuomas.katila@intel.com>
Signed-off-by: Tuomas Katila <tuomas.katila@intel.com>
I dropped the preferred allocation policy as it would require more than one NPU to exist and that's not expected as the NPUs are tied to CPUs. |
* Core Ultra Series 1 | ||
* Core Ultra Series 2 | ||
* Core Ultra 200V Series |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO code names like MeteorLake etc are also useful, because that's e.g. how Wikipedia refers to them: https://en.wikipedia.org/wiki/Meteor_Lake
=> Maybe code names could be in parenthesis?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was requested to use the official names. :) But I agree that the codenames are familiar for people, maybe even more familiar.
No description provided.