RFR: 8312585: Rename DisableTHPStackMitigation flag to THPStackMitigation

David Holmes dholmes at openjdk.org
Mon Jul 24 12:11:39 UTC 2023


On Mon, 24 Jul 2023 09:02:59 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

> The flag newly added by [JDK-8312182](https://bugs.openjdk.org/browse/JDK-8312182) is prompting the use of `-XX:+DisableTHPStackMitigation` to disable the THP stack mitigation, thus allowing THP in thread stacks. This double negation does not read well, and not in line with other mitigation flags like `IntelJccErratumMitigation`.
> 
> It would be better to rename the flag to avoid double-negation, before it proliferates to other JDK releases.
> 
> (I would have the same comment during the original review, but missed it :P)
> 
> Additional testing: 
>  - [ ] GHA
>  - [x] Linux x86_64 fastdebug, affected test

I disagree. This name is exactly what is intended - we disable a mitigation/workaround. It's name is consistent with previous flags of this kind DisableXXXWorkAround IIRC.

I also don't see a "double negation" here - naming a flag DisableX is not in itself double-negation.

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

PR Comment: https://git.openjdk.org/jdk/pull/14992#issuecomment-1647783084
PR Comment: https://git.openjdk.org/jdk/pull/14992#issuecomment-1647786327


More information about the hotspot-runtime-dev mailing list