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

configs/validate: looser validation for RDT #3382

Merged
merged 1 commit into from Mar 7, 2022

Conversation

marquiz
Copy link
Contributor

@marquiz marquiz commented Feb 18, 2022

Don't require CAT or MBA because we don't detect those correctly (we
don't support L2 or L3DATA/L3CODE for example, and in the future
possibly even more). With plain "ClosId mode" we don't really care: we
assign the container to a pre-configured CLOS without trying to do
anything smarter.

Moreover, this was a duplicate/redundant check anyway, as for CAT and
MBA there is another specific sanity check that is done if L3 or MB
is specified in the config.

Don't require CAT or MBA because we don't detect those correctly (we
don't support L2 or L3DATA/L3CODE for example, and in the future
possibly even more). With plain "ClosId mode" we don't really care: we
assign the container to a pre-configured CLOS without trying to do
anything smarter.

Moreover, this was a duplicate/redundant check anyway, as for CAT and
MBA there is another specific sanity check that is done if L3 or MB
is specified in the config.

Signed-off-by: Markus Lehtonen <markus.lehtonen@intel.com>
@marquiz
Copy link
Contributor Author

marquiz commented Feb 18, 2022

ping @kolyshkin

Copy link
Contributor

@kolyshkin kolyshkin left a comment

Choose a reason for hiding this comment

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

LGTM

This needs to be backported to release-1.1 branch. @marquiz can you open a backport PR (once this one is merged)? For example, see #3355

@kolyshkin kolyshkin added area/intelrdt backport/todo/1.1 A PR in main branch which needs to be backported to release-1.1 easy-to-review labels Feb 18, 2022
@marquiz
Copy link
Contributor Author

marquiz commented Feb 19, 2022

Thanks @kolyshkin for the review.

This needs to be backported to release-1.1 branch. @marquiz can you open a backport PR (once this one is merged)? For example, see #3355

Roger, will do 👍

@marquiz
Copy link
Contributor Author

marquiz commented Feb 21, 2022

ping @AkihiroSuda @thaJeztah, PTAL

@AkihiroSuda AkihiroSuda merged commit f7bce6b into opencontainers:main Mar 7, 2022
@kolyshkin
Copy link
Contributor

@marquiz please open a backport to release-1.1 branch

@marquiz marquiz deleted the devel/rdt-validation branch March 8, 2022 07:52
@marquiz
Copy link
Contributor Author

marquiz commented Mar 8, 2022

@marquiz please open a backport to release-1.1 branch

Check! #3406

@kolyshkin kolyshkin added backport/done/1.1 A PR in main branch which was backported to release-1.1 and removed backport/todo/1.1 A PR in main branch which needs to be backported to release-1.1 labels Mar 8, 2022
@kolyshkin kolyshkin mentioned this pull request Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/intelrdt backport/done/1.1 A PR in main branch which was backported to release-1.1 easy-to-review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants