feat: vxpu sopport #1016

[ouyangluwei163]

What type of PR is this?
/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #1016

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[hami-robott]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ouyangluwei163
Once this PR has been reviewed and has the lgtm label, please assign wawa0210 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

Attention: Patch coverage is 27.05882% with 124 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
pkg/device/kunlunxin/device.go	24.37%	118 Missing and 3 partials ⚠️
pkg/device/devices.go	70.00%	2 Missing and 1 partial ⚠️

Flag	Coverage Δ
unittests	61.82% <27.05%> (-1.31%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
pkg/device/devices.go	73.53% <70.00%> (-0.12%)	⬇️
pkg/device/kunlunxin/device.go	24.37% <24.37%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lengrongfu]

This cores percentage and memory is same, Is there any special reason? can't a similar setup as Nvidia vgpu be achieved?

[lengrongfu]

Is this because xpu can only achieve three slicing specifications: 1, 1/2 and 1/4?

[wawa0210]

/hold

This PR can be put on hold. The maintainer team is refactoring the scheduling code for different GPUs and the basic support for Kunlun. We can review this PR after the update.