RFR: 8366847: JFR reports incorrect number of cores on hybrid CPU [v3]

Yasumasa Suenaga ysuenaga at openjdk.org
Thu Oct 2 08:44:06 UTC 2025


On Thu, 2 Oct 2025 07:58:08 GMT, Erik Gahlin <egahlin at openjdk.org> wrote:

> but promoting the field to a long value might be too disruptive. It's a value users are likely to extract programmatically.

If the data size is important than showing "N/A", I think we can set "0" for number of cores as I proposed [at first](https://openjdk.github.io/cr/?repo=jdk&pr=27080&range=00). But you said before that it should not be a problem to change to type long: https://github.com/openjdk/jdk/pull/27080#issuecomment-3270024207

Which is better? I think it is better not to change data size rather than showing "N/A" for compatibility. I think it is whether it feels natural for JFR that "0" means "N/A".

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

PR Comment: https://git.openjdk.org/jdk/pull/27080#issuecomment-3359903487


More information about the hotspot-jfr-dev mailing list