[crac] RFR: 8368929: [CRaC] Move CPUFeatures check to C/R engine [v11]
Radim Vansa
rvansa at openjdk.org
Thu Oct 9 14:33:00 UTC 2025
> Right now the logic checking if CPU features used before checkpoint match current CPU features is in VM code. VM stores and retrieves CPU features through C/R API's user_data extension. This is convenient when we have a single image that can be either accepted or rejected, but does not offer the flexibility for C/R engine to select the best image for current execution environment.
>
> The goal of this issue is to move to a declarative API that will express the requirements using more abstract means, labels (for CPU architecture) and bitmaps (for CPU features).
Radim Vansa has updated the pull request incrementally with one additional commit since the last revision:
Apply suggestions from code review
Co-authored-by: Timofei Pushkin <pushkin.td at gmail.com>
-------------
Changes:
- all: https://git.openjdk.org/crac/pull/266/files
- new: https://git.openjdk.org/crac/pull/266/files/71ccd10c..cc676f7a
Webrevs:
- full: https://webrevs.openjdk.org/?repo=crac&pr=266&range=10
- incr: https://webrevs.openjdk.org/?repo=crac&pr=266&range=09-10
Stats: 8 lines in 3 files changed: 1 ins; 3 del; 4 mod
Patch: https://git.openjdk.org/crac/pull/266.diff
Fetch: git fetch https://git.openjdk.org/crac.git pull/266/head:pull/266
PR: https://git.openjdk.org/crac/pull/266
More information about the crac-dev
mailing list