[crac] RFR: RFC: -XX:CPUFeatures=0xnumber for CPU migration [v8]

[Radim Vansa]

On Wed, 1 Mar 2023 11:46:18 GMT, Jan Kratochvil <duke at openjdk.org> wrote:

>> I think in this PR we can concentrate on CPU features, as CPU core number is a different problem, that can arise even with the same feature set.
>> 
>> As for ifunc change and Watcher Thread problems, this won't happen if we re-execute with GLIBC_TUNABLES. And re-execute will also resolve the maintainability concern.
>
>> I think in this PR we can concentrate on CPU features, as CPU core number is a different problem, that can arise even with the same feature set.
> 
> I could split the patch but it is not testable/usable without the CPU count fix/hack.
> 
> But I am now preparing the IFUNC patch for glibc upstreaming, whether it will be accepted or not.
> 
> As long as you do not want a temporary solution in CRaC we can suspend this patch until glibc upstreaming gets resolved.

Hi @jankratochvil , the checks still show some trouble with whitespaces (tabs). Could you also merge in the current `crac` branch - looks like this does not use the workflow including CRaC tests.

-------------

PR Comment: https://git.openjdk.org/crac/pull/41#issuecomment-1525077214